Skip to main content
Glama

Buyer search run status

exim__run__status
Read-onlyIdempotent

Returns the live status of a buyer search run by run id or collection id: progress, counts and credits reserved, charged or refunded.

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": "exim__run__status"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdNoRun UUID returned by `exim search run confirmed true`.
collectionIdNoCollection UUID; resolves the latest run for that collection.

Output Schema

NameRequiredDescriptionDefault
dataYes
statsNo
_debugNo
summaryYes
warningsNo
nextActionsYes
correlationIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / data / properties / context / anyOf
      Added value: +[
      +  {
      +    "type": [
      +      "null",
      +      "boolean",
      +      "number",
      +      "string",
      +      "array",
      +      "object"
      +    ]
      +  },
      +  {
      +    "additionalProperties": true,
      +    "properties": {
      +      "referenced": {
      +        "type": "boolean"
      +      },
      +      "rowCount": {
      +        "type": "integer"
      +      },
      +      "url": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "referenced",
      +      "rowCount",
      +      "url"
      +    ],
      +    "type": "object"
      +  }
      +]
    • removedOutput schema / properties / data / properties / context / type
      Removed value: -[
      -  "null",
      -  "boolean",
      -  "number",
      -  "string",
      -  "array",
      -  "object"
      -]
    • changedOutput schema / properties / data / properties / items / anyOf
      Previous value: -[
      -  {
      -    "items": {
      -      "$ref": "#/$defs/value0"
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {
      +      "anyOf": [
      +        {
      +          "$ref": "#/$defs/value0"
      +        },
      +        {
      +          "additionalProperties": false,
      +          "properties": {
      +            "exportUrl": {
      +              "type": "string"
      +            },
      +            "payloadBytes": {
      +              "type": "integer"
      +            },
      +            "rowCount": {
      +              "type": "integer"
      +            },
      +            "token": {
      +              "type": "string"
      +            },
      +            "url": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "exportUrl",
      +            "payloadBytes",
      +            "rowCount",
      +            "token",
      +            "url"
      +          ],
      +          "type": "object"
      +        }
      +      ]
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. Added
  3. Removed
  4. Added
  5. Removed
  6. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description only adds that the status is 'live' (real-time rather than cached) and that credit states (reserved/charged/refunded) appear — detail that largely duplicates the output schema. Nothing is said about terminal states, staleness, or errors for unknown ids.

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?

A single front-loaded sentence with the resource, the addressing options, and the returned content in that order. No filler, no restatement of 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?

With rich annotations, an output schema, and fully documented parameters, the description covers enough to call the tool correctly. The remaining gap is relational: it does not place this tool next to exim__run__summary or explain lifecycle/terminal-state semantics for a long-running search.

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 coverage is 100% and both parameters carry their own descriptions, including that collectionId 'resolves the latest run for that collection', which is the key disambiguator. The description's 'by run id or collection id' loosely conveys the mutual-exclusive choice the JSON schema encodes, but adds no format or resolution detail of its own.

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?

Names a specific verb and resource: 'Returns the live status of a buyer search run', and identifies the two addressing keys (run id or collection id). It is clear what the tool does, but it never distinguishes itself from the sibling exim__run__summary, which an agent could easily confuse with a status read.

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

Usage Guidelines3/5

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

Usage is only implied — an agent must infer this is for checking progress of a search run it already launched. There is no statement of when to prefer this over exim__run__summary, and no guidance on polling cadence or when the run is finished.

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.