Skip to main content
Glama

discover_brand_domains_status

Read-onlyIdempotent

Poll the status and progress of an async brand-domain discovery operation, returning queued, running, completed, or failed states.

Instructions

Poll the status of an async brand-domain discovery started with discover_brand_domains_start. Returns status (queued | running | completed | failed) and progress. Owner-scoped — operationIds owned by other principals surface as notFound.

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": {
      "operationId": "<operationId>"
    },
    "name": "discover_brand_domains_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoOutput verbosity.
operationIdYesOperation ID returned by discover_brand_domains_start.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.111.2
    • changedInput schema / properties / format / description
      Previous value: -"Output verbosity. Auto-detected if omitted."New value: +"Output verbosity."
  2. Changed2 schema fields changedv3.103.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / format
      Added value: +{
      +  "description": "Output verbosity. Auto-detected if omitted.",
      +  "enum": [
      +    "full",
      +    "compact"
      +  ],
      +  "type": "string"
      +}
  3. Addedv3.37.0
  4. Removedv3.31.1
  5. First observedv3.29.7

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent and non-destructive, so the bar is lower, yet the description adds real behavior: it enumerates the four returnable states and discloses that operations owned by other principals surface as notFound. That ownership/authorization disclosure is the kind of detail annotations do not carry. It omits any note on rate limits or recommended polling interval.

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: purpose and lifecycle linkage first, then return states, then the scoping caveat. Nothing is redundant and the most decision-relevant fact is front-loaded.

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 no output schema, the description compensates by naming the status values and the progress field, and it covers the key failure mode for a scoped polling tool. Only polling behavior over time (retry/interval, terminal conditions) is left implicit.

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 coverage is 100%, giving a baseline of 3, but the description adds meaning to operationId beyond the schema by tying it to discover_brand_domains_start and explaining that a foreign-owned operationId resolves to notFound. The format parameter's verbosity trade-off is left 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?

Uses a specific verb (poll) plus resource (status of async brand-domain discovery) and explicitly anchors to the sibling that creates the operation, discover_brand_domains_start. An agent can separate this from the start/findings siblings without reading any schema.

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?

The word "Poll" and the reference to the operation started via discover_brand_domains_start make the when-to-use case clear and imply the start-then-poll workflow. It stops short of explicit guidance on polling cadence or the terminal condition (e.g., stop once completed/failed), so there are no stated exclusions or alternatives beyond the implied one.

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

Deploy Server

Other Tools