MCP Tools Reference: container.googleapis.com

Tool: get_k8s_logs

Gets logs from a Kubernetes container in a pod. This is similar to running kubectl logs .

The following sample demonstrate how to use curl to invoke the get_k8s_logs MCP tool.

Curl Request
  
curl  
--location  
 'https://container.googleapis.com/mcp' 
  
 \ 
--header  
 'content-type: application/json' 
  
 \ 
--header  
 'accept: application/json, text/event-stream' 
  
 \ 
--data  
 '{ 
 "method": "tools/call", 
 "params": { 
 "name": "get_k8s_logs", 
 "arguments": { 
 // provide these details according to the tool' 
s  
MCP  
specification  
 } 
  
 } 
,  
 "jsonrpc" 
:  
 "2.0" 
,  
 "id" 
:  
 1 
 } 
 ' 
  

Input Schema

KubeLogsRequest is the request message for retrieving Kubernetes logs.

GetK8SLogsRequest

JSON representation
 { 
 "parent" 
 : 
 string 
 , 
 "name" 
 : 
 string 
 , 
 "namespace" 
 : 
 string 
 , 
 "allContainers" 
 : 
 boolean 
 , 
 "container" 
 : 
 string 
 , 
 "previous" 
 : 
 boolean 
 , 
 "timestamps" 
 : 
 boolean 
 , 
 "tail" 
 : 
 string 
 , 
 // Union field since_filter 
can be only one of the following: 
 "sinceTime" 
 : 
 string 
 , 
 "since" 
 : 
 string 
 // End of list of possible types for union field since_filter 
. 
 } 
Fields
parent

string

Required. The cluster to retrieve logs from. Format: projects/{project}/locations/{location}/clusters/{cluster}

name

string

Required. The name of the resource to retrieve logs from. This can be a pod name (e.g. "my-pod") or a type/name (e.g. "deployment/my-deployment"). If a type is not specified, "pod" is assumed.

namespace

string

Optional. The namespace of the resource. If not specified, "default" is used.

allContainers

boolean

Optional. If true, retrieve logs from all containers in the pod.

container

string

Optional. The name of the container to retrieve logs from. If not specified, logs from the first container are returned.

previous

boolean

Optional. If true, retrieve logs from the previous instantiation of the container.

timestamps

boolean

Optional. If true, include timestamps in the log output.

tail

string ( int64 format)

Optional. The number of lines from the end of the logs to show.

Union field since_filter . Only one of since_time and since can be set. since_filter can be only one of the following:
sinceTime

string ( Timestamp format)

Optional. Retrieve logs since this time (RFC3339). e.g. "2024-08-30T06:00:00Z".

Uses RFC 3339, where generated output will always be Z-normalized and use 0, 3, 6 or 9 fractional digits. Offsets other than "Z" are also accepted. Examples: "2014-10-02T15:01:23Z" , "2014-10-02T15:01:23.045123456Z" or "2014-10-02T15:01:23+05:30" .

since

string ( Duration format)

Optional. Retrieve logs since this duration ago (e.g. "1h", "10m").

A duration in seconds with up to nine fractional digits, ending with ' s '. Example: "3.5s" .

Timestamp

JSON representation
 { 
 "seconds" 
 : 
 string 
 , 
 "nanos" 
 : 
 integer 
 } 
Fields
seconds

string ( int64 format)

Represents seconds of UTC time since Unix epoch 1970-01-01T00:00:00Z. Must be between -62135596800 and 253402300799 inclusive (which corresponds to 0001-01-01T00:00:00Z to 9999-12-31T23:59:59Z).

nanos

integer

Non-negative fractions of a second at nanosecond resolution. This field is the nanosecond portion of the duration, not an alternative to seconds. Negative second values with fractions must still have non-negative nanos values that count forward in time. Must be between 0 and 999,999,999 inclusive.

Duration

JSON representation
 { 
 "seconds" 
 : 
 string 
 , 
 "nanos" 
 : 
 integer 
 } 
Fields
seconds

string ( int64 format)

Signed seconds of the span of time. Must be from -315,576,000,000 to +315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years

nanos

integer

Signed fractions of a second at nanosecond resolution of the span of time. Durations less than one second are represented with a 0 seconds field and a positive or negative nanos field. For durations of one second or more, a non-zero value for the nanos field must be of the same sign as the seconds field. Must be from -999,999,999 to +999,999,999 inclusive.

Output Schema

KubeLogsResponse is the response message for retrieving Kubernetes logs.

GetK8SLogsResponse

JSON representation
 { 
 "logs" 
 : 
 string 
 , 
 "errors" 
 : 
 [ 
 { 
 object (  Status 
 
) 
 } 
 ] 
 } 
Fields
logs

string

The logs from the resources.

errors[]

object ( Status )

Errors encountered during log retrieval.

Status

JSON representation
 { 
 "code" 
 : 
 integer 
 , 
 "message" 
 : 
 string 
 , 
 "details" 
 : 
 [ 
 { 
 "@type" 
 : 
 string 
 , 
 field1 
 : 
 ... 
 , 
 ... 
 } 
 ] 
 } 
Fields
code

integer

The status code, which should be an enum value of google.rpc.Code .

message

string

A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the google.rpc.Status.details field, or localized by the client.

details[]

object

A list of messages that carry the error details. There is a common set of message types for APIs to use.

An object containing fields of an arbitrary type. An additional field "@type" contains a URI identifying the type. Example: { "id": 1234, "@type": "types.example.com/standard/id" } .

Any

JSON representation
 { 
 "typeUrl" 
 : 
 string 
 , 
 "value" 
 : 
 string 
 } 
Fields
typeUrl

string

Identifies the type of the serialized Protobuf message with a URI reference consisting of a prefix ending in a slash and the fully-qualified type name.

Example: type.googleapis.com/google.protobuf.StringValue

This string must contain at least one / character, and the content after the last / must be the fully-qualified name of the type in canonical form, without a leading dot. Do not write a scheme on these URI references so that clients do not attempt to contact them.

The prefix is arbitrary and Protobuf implementations are expected to simply strip off everything up to and including the last / to identify the type. type.googleapis.com/ is a common default prefix that some legacy implementations require. This prefix does not indicate the origin of the type, and URIs containing it are not expected to respond to any requests.

All type URL strings must be legal URI references with the additional restriction (for the text format) that the content of the reference must consist only of alphanumeric characters, percent-encoded escapes, and characters in the following set (not including the outer backticks): /-.~_!$&()*+,;= . Despite our allowing percent encodings, implementations should not unescape them to prevent confusion with existing parsers. For example, type.googleapis.com%2FFoo should be rejected.

In the original design of Any , the possibility of launching a type resolution service at these type URLs was considered but Protobuf never implemented one and considers contacting these URLs to be problematic and a potential security issue. Do not attempt to contact type URLs.

value

string ( bytes format)

Holds a Protobuf serialization of the type described by type_url.

A base64-encoded string.

Tool Annotations

Destructive Hint: ❌ | Idempotent Hint: ✅ | Read Only Hint: ✅ | Open World Hint: ❌

Create a Mobile Website
View Site in Mobile | Classic
Share by: