Skip to main content
Glama

Collect a deep creator search

flypost_get_creator_search
Read-only

Collect the results of a flypost_deep_search_creators run that was still running. Waits up to about 90 seconds; while status is still 'running', call again later.

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": {
      "job_id": "<job_id>"
    },
    "name": "flypost_get_creator_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesFrom flypost_deep_search_creators.
regionsNoThe same regions the search was started with.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered structurally; the description adds the genuinely useful behavioral fact that the call blocks for up to about 90 seconds and may need to be repeated. It does not address whether repeated polling consumes credits or invalidates the job id, which would matter for a polling tool.

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

Conciseness5/5

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

Two tight sentences, front-loaded with the action and followed by the polling constraint. No filler and nothing redundant with the title.

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

Completeness4/5

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

For a two-parameter read-only polling tool with full schema coverage and annotations, the description covers the essentials: what is fetched, the blocking window, and the retry condition. With no output schema present, a brief note on what the results contain would make it complete.

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% and both parameters are already documented in-schema ('From flypost_deep_search_creators', 'The same regions the search was started with'). The description adds no additional meaning about job_id or regions, so the baseline of 3 applies.

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

Purpose4/5

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

The description uses a concrete verb and resource ('collect the results of a flypost_deep_search_creators run') and names the exact sibling tool whose job it polls, so the agent can distinguish it from the search-starting tool. It stops short of stating what the collected results actually are, which keeps it from being fully self-describing.

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 when-to-use context: this is for a run that came back 'still running', and it explicitly instructs to call again later while the status remains 'running'. It does not say what to do if the job has failed or expired, so there is a small gap around the non-running, non-success path.

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.