Skip to main content
Glama

Get Library upload status

get_library_upload_status
Read-only

Returns status for one or more Library uploads. Pass upload_handles, or pass the session_token from create_library_upload_session to list every file the user uploaded in that uploader, which is how to find files picked in the in-chat uploader or the upload page. Stop polling an item at ready, unavailable, failed, expired, or cancelled. Processing items may include their current stage. A ready item includes its content id and a short-lived selection token. Unavailable means the file is in Library but has no usable source text. A per-item error means the status could not be read; retry it only when retryable is true. Other items remain usable.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_library_upload_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_tokenNo
upload_handlesNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnlyHint and destructiveHint annotations, the description explains terminal statuses, processing stages, what a ready item contains, what unavailable means, and how per-item errors should be retried only when retryable is true. This is substantial behavioral context for correctly interpreting and polling upload status.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is front-loaded with the core purpose and then moves through invocation, polling, and status semantics in a logical order. It is dense but nearly every sentence adds operational value, though the long paragraph could be slightly tighter or more structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must explain return behavior, and it does so by documenting terminal statuses, processing-stage details, ready-item fields, unavailable semantics, and partial per-item errors. That is complete enough for an agent to invoke this read-only polling tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description carries the parameter meaning by explaining that upload_handles are passed directly and that session_token lists every file uploaded in that uploader. It does not cover constraints such as the maximum of 10 handles, uniqueness, or what happens if both parameters are supplied or neither is supplied.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: it returns status for one or more Library uploads. It also scopes the call to Library uploads and references create_library_upload_session as the source of the session_token, which helps distinguish it from unrelated upload tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains the two invocation modes, tells the agent to pass upload_handles or a session_token, and notes that the session token is how to find files picked in the in-chat uploader or upload page. It also gives polling stop conditions, but it does not explicitly name alternatives such as get_lesson_upload_status or state exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources