Skip to main content
Glama

Market Brew

Get crawl seed import progress

get_deep_crawl_import
Read-onlyIdempotent

Use this when the user asks to get crawl seed import progress. Returns only data visible to the linked Market Brew account.

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": {
      "website": "<website>",
      "importId": "<importId>"
    },
    "name": "get_deep_crawl_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
websiteYes
importIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / importId / $ref
      Added value: +"#/properties/website/anyOf/0"
    • removedInput schema / properties / importId / anyOf
      Removed value: -[
      -  {
      -    "minLength": 1,
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]
    • changedInput schema / properties / website / anyOf
      Previous value: -[
      -  {
      -    "minLength": 1,
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]New value: +[
      +  {
      +    "anyOf": [
      +      {
      +        "exclusiveMinimum": 0,
      +        "maximum": 9007199254740991,
      +        "minimum": -9007199254740991,
      +        "type": "integer"
      +      },
      +      {
      +        "pattern": "^[1-9][0-9]{0,17}$",
      +        "type": "string"
      +      }
      +    ]
      +  },
      +  {
      +    "maxLength": 254,
      +    "minLength": 1,
      +    "type": "string"
      +  }
      +]
  2. First observed

TDQS

C2.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds one genuinely new behavioral fact: results are scoped to the linked Market Brew account, which tells the agent that missing records may be a permissions issue rather than a bad importId. Nothing else about behavior (polling cadence, whether progress is final) is disclosed.

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

Conciseness3/5

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

Two short sentences with no filler and the access-scope caveat placed second, so it reads cleanly. However, the first sentence is pure duplication of the title, so the brevity reflects under-specification rather than disciplined editing.

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

Completeness2/5

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

There is no output schema, so the description carries the burden of telling the agent what a 'progress' response looks like — counts, percentages, state enum, terminal condition — and it says nothing. For a two-required-parameter lookup tool whose results drive polling decisions, an agent cannot tell from this definition whether one call suffices or whether it must be repeated.

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

Parameters2/5

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

Schema description coverage is 0% and both parameters (website, importId) are required, yet the description says nothing about them — not what 'website' accepts (numeric site id vs. domain string, since the schema allows either) and not how to obtain an importId. The parameter names are self-evident identifiers, which prevents a 1, but the description does no compensating work for the coverage gap.

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

Purpose2/5

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

The sentence "Use this when the user asks to get crawl seed import progress" is a near-verbatim restatement of the tool title 'Get crawl seed import progress'. It never states what the returned progress consists of (status, counts, per-URL state) nor distinguishes it from siblings such as get_deep_crawl_seed or list_deep_crawl_seed_attempts.

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

Usage Guidelines2/5

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

The only usage cue is circular: use it when the user asks for it. There is no when-not to use it, no prerequisite that a valid importId must already exist, and no pointer to the seed-level or attempts-level siblings that would be the alternative when an agent needs broader crawl data.

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