Skip to main content
Glama

Market Brew

Export crawl seed attempt history

export_deep_crawl_seed_attempts
Read-onlyIdempotent

Use this when the user asks to export crawl seed attempt history. 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>",
      "seedId": "<seedId>"
    },
    "name": "export_deep_crawl_seed_attempts"
  }
}

Input Schema

NameRequiredDescriptionDefault
offsetNo
seedIdYes
websiteYes
maxCharsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / offset / maximum
      Added value: +9007199254740991
    • removedInput schema / properties / seedId / $ref
      Removed value: -"#/properties/website/anyOf/0"
    • addedInput schema / properties / seedId / anyOf
      Added value: +[
      +  {
      +    "exclusiveMinimum": 0,
      +    "maximum": 9007199254740991,
      +    "type": "integer"
      +  },
      +  {
      +    "pattern": "^[1-9][0-9]{0,17}$",
      +    "type": "string"
      +  }
      +]
    • changedInput schema / properties / website / anyOf
      Previous 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"
      -  }
      -]New value: +[
      +  {
      +    "anyOf": [
      +      {
      +        "exclusiveMinimum": 0,
      +        "maximum": 9007199254740991,
      +        "type": "integer"
      +      },
      +      {
      +        "pattern": "^[1-9][0-9]{0,17}$",
      +        "type": "string"
      +      }
      +    ]
      +  },
      +  {
      +    "maxLength": 254,
      +    "minLength": 1,
      +    "type": "string"
      +  }
      +]
  2. Changed5 schema fields changed
    • removedInput schema / properties / maxChars / description
      Removed value: -"Maximum export characters to return."
    • removedInput schema / properties / offset / description
      Removed value: -"Character offset into the export."
    • addedInput schema / properties / seedId / $ref
      Added value: +"#/properties/website/anyOf/0"
    • removedInput schema / properties / seedId / 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"
      +  }
      +]
  3. First observed

TDQS

C2.8/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 the safety profile is fully covered structurally. The description does add genuine value with the data-boundary note that only data visible to the linked Market Brew account is returned, which matters for authorization expectations. It omits two consequential behaviors, though: the offset-based pagination and the maxChars cap (default 50000) that can silently truncate an export.

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 trigger condition front-loaded, so it is efficient. The brevity comes at the cost of under-specification rather than being tight, information-dense prose.

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?

For a four-parameter export tool with zero schema description coverage and no output schema, the description should carry most of the burden and does not. An agent cannot tell how results are paginated, when output will be cut off by maxChars, or what an export returns versus a list.

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% across four parameters, and the description compensates for none of them. Neither required parameter (website, seedId) nor the two behavioral knobs (offset, maxChars) is explained, so the agent gets no hint that maxChars controls export truncation or what identifier forms seedId accepts.

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

Purpose3/5

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

The description pairs the verb "export" with the resource "crawl seed attempt history," so the basic operation is identifiable. However, the phrasing largely restates the title verbatim, and it never distinguishes an export from the numerous listing siblings such as list_deep_crawl_seed_attempts, leaving the agent to infer that "export" implies a bulk/file-producing variant.

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?

"Use this when the user asks to export crawl seed attempt history" gives a triggering condition, but it is a near-circular restatement of the tool name rather than real routing guidance. No alternatives are named, no exclusions are stated, and nothing tells the agent when to prefer this over list_deep_crawl_seed_attempts or export_deep_crawl_seed_errors.

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