Skip to main content
Glama

Playbook

by com.playbook
OverviewDiscussionsAdmin

Get import status

get_import
Read-only

Read an import run's progress: status (pending, active, completed, canceled), cancel_reason, scanning (still listing folders), the target board_token (files are in sub-boards named after each folder), and files counts (total, pending, completed, skipped, failed). skipped includes files already on the board unchanged. cancel_reason on canceled: overlimit — out of storage or assets, or the next file would have crossed into storage overage the workspace has not agreed to (nothing past that point was stored); incomplete — some files failed; failed_to_start — could not start, e.g. sustained provider rate limiting; oauth_credential_deleted / target_collection_deleted — the connection or board was removed; blocked — blocked by an admin. Poll no more than every 15–30 seconds.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenYesImport token returned by import_from_google_drive or import_from_dropbox
organizationNoWorkspace slug, as returned by list_organizations. Omit it when the account has a single workspace — it is then resolved from your token. Pass it only when the account has several, or when you mean a workspace other than the obvious one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / context
      Removed value: -{
-  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "token",
-  "context"
-]New value: +[
+  "token"
+]
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the read-only safety profile, and the description goes well beyond them by documenting a rate limit, the meaning of `skipped`, and the full semantics of every `cancel_reason` value (including that nothing past an overlimit point was stored). This is exactly the operational context an agent needs and cannot get from structured fields.

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?

Front-loaded with the core purpose, and the dense enumeration of status/cancel_reason values is justified because no output schema exists to carry that information. The backtick-heavy value list is slightly unwieldy but every clause carries meaning.

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?

With no output schema, the description correctly shoulders the burden of explaining the return payload, and it does so thoroughly, including terminal-state interpretation. Combined with annotations covering safety, an agent has everything needed to call and interpret this tool.

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

Parameters3/5

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

Schema description coverage is 100%, so both `token` and `organization` are already fully documented in the schema, and the description adds no further parameter guidance. The mention of `board_token` and `files` describes returned fields, not inputs, so the baseline 3 is appropriate.

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?

States a specific verb and resource ('Read an import run's progress') and immediately enumerates the fields it returns, so the agent knows exactly what this retrieves. The `token` semantics tie it to import_from_google_drive/import_from_dropbox, distinguishing it from the tools that start imports rather than report on them.

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?

Clear context is given: this is the polling tool for an in-progress import, with an explicit cadence constraint ('Poll no more than every 15-30 seconds'). It does not name an alternative or state when not to use it, so it stops short of full routing guidance, but the intended usage is unambiguous.

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

All Playbook toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources