Skip to main content
Glama

mcp-notion__notion-get-async-task

Read-onlyIdempotent

Retrieves the current status of an async task that was started by another tool (for example, "create_pages" called with "allow_async": true).

The status is one of "queued", "running", "retrying", "succeeded", or "failed". When the task has succeeded, the operation's result is included; when it has failed, an error is included instead.

Poll this tool with the "task_id" from the original tool's "async_task" response. Wait briefly between polls — the original response includes a suggested backoff.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "task_id": "<task_id>"
    },
    "name": "mcp-notion__notion-get-async-task"
  }
}

Input Schema

NameRequiredDescriptionDefault
skillNoFor tracking only: the name of the agent skill you are following for this task, such as notion-meeting-prep. Omit if you are not following a skill.
site_idNoSite to run this tool on: ded71e55-0da4-4a52-8f14-1224fa9979b9 (https://mcp.notion.com/mcp)
task_idYesThe ID of the async task to retrieve, as returned in the async_task response of the tool that started it.
instructions_versionNoNotion setup instructions version, such as 0.0.2. Omit if unknown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, and the description adds real value on top: the enumerated status lifecycle (queued/running/retrying/succeeded/failed) and what the payload contains on success versus failure. It stops short of describing pagination or timeout behavior, but for a status-poll tool the state model is the key disclosure.

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 purpose, then status semantics, then polling instructions, plus a compact example. The trailing sentence about the server marking it read-only is redundant with the annotations and slightly awkward, but the rest is tight and earns its space.

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?

For a single-purpose polling tool with no output schema, the description covers everything an agent needs: where the ID comes from, the possible states, what success and failure return, and how to pace polling. Nothing material is missing.

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?

Schema description coverage is 100%, so a baseline of 3 applies, and the description goes further by tracing task_id to its origin in the "async_task" response and tying polling cadence to the original response's backoff hint. The remaining parameters (skill, site_id, instructions_version) are left entirely to the schema.

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 ("Retrieves the current status of an async task") and scopes it to tasks started by other tools, with a concrete example of the originating tool ("create_pages" with "allow_async": true). No sibling in the catalog does this, and the description makes that distinct role obvious.

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

Usage Guidelines5/5

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

Explicitly tells the agent how to use it: poll with the "task_id" from the original tool's "async_task" response, and wait briefly between polls using the suggested backoff. That is a complete usage protocol rather than an implied one, and no alternative tool is needed for this job.

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