Tool: list_transfer_logs
List transfer logs for a transfer run by its resource name.
The following example shows a MCP call to list transfer logs for a transfer run.
list_transfer_logs(parent="projects/myproject/locations/myregion/transferConfigs/mytransferconfig/runs/mytransferrun")
The following sample demonstrate how to use curl to invoke the list_transfer_logs MCP tool.
| Curl Request |
|---|
curl --location 'https://bigquerydatatransfer.googleapis.com/mcp' \ --header 'content-type: application/json' \ --header 'accept: application/json, text/event-stream' \ --data '{ "method": "tools/call", "params": { "name": "list_transfer_logs", "arguments": { // provide these details according to the tool's MCP specification } }, "jsonrpc": "2.0", "id": 1 }' |
Input Schema
A request to get user facing log messages associated with data transfer run.
ListTransferLogsRequest
| JSON representation |
|---|
{
"parent": string,
"pageToken": string,
"pageSize": integer,
"messageTypes": [
enum ( |
| Fields | |
|---|---|
parent |
Required. Transfer run name. If you are using the regionless method, the location must be
If you are using the regionalized method, the name should be in the following form:
|
pageToken |
Pagination token, which can be used to request a specific page of |
pageSize |
Page size. The default page size is the maximum value of 1000 results. |
messageTypes[] |
Message types to return. If not populated - INFO, WARNING and ERROR messages are returned. |
MessageSeverity
Represents data transfer user facing message severity.
| Enums | |
|---|---|
MESSAGE_SEVERITY_UNSPECIFIED |
No severity specified. |
INFO |
Informational message. |
WARNING |
Warning message. |
ERROR |
Error message. |
Output Schema
The returned list transfer run messages.
ListTransferLogsResponse
| JSON representation |
|---|
{
"transferMessages": [
{
object ( |
| Fields | |
|---|---|
transferMessages[] |
Output only. The stored pipeline transfer messages. |
nextPageToken |
Output only. The next-pagination token. For multiple-page list results, this token can be used as the |
TransferMessage
| JSON representation |
|---|
{
"messageTime": string,
"severity": enum ( |
| Fields | |
|---|---|
messageTime |
Time when message was logged. 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: |
severity |
Message severity. |
messageText |
Message text. |
Timestamp
| JSON representation |
|---|
{ "seconds": string, "nanos": integer } |
| Fields | |
|---|---|
seconds |
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 |
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. |
MessageSeverity
Represents data transfer user facing message severity.
| Enums | |
|---|---|
MESSAGE_SEVERITY_UNSPECIFIED |
No severity specified. |
INFO |
Informational message. |
WARNING |
Warning message. |
ERROR |
Error message. |
Tool Annotations
Destructive Hint: ❌ | Idempotent Hint: ✅ | Read Only Hint: ✅ | Open World Hint: ❌