Skip to main content
Glama

Market Brew

Export crawl seed inventory

export_deep_crawl_seeds
Read-onlyIdempotent

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

Input Schema

NameRequiredDescriptionDefault
offsetNo
websiteYes
maxCharsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / offset / maximum
      Added value: +9007199254740991
    • 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. Changed3 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."
    • 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.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds one genuinely new behavioral fact — output is scoped to data visible to the linked Market Brew account — but says nothing about the export medium, size limits, or what maxChars truncation means for the result.

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

Conciseness4/5

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

Two short sentences with no filler and the trigger stated up front, so nothing is wasted. The brevity is efficient but tips into under-specification rather than tight completeness.

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 3-parameter export tool with no output schema and no parameter documentation, the description leaves the agent guessing about the export format, whether results paginate via offset, and how maxChars affects the payload. Only the account-visibility caveat is covered, which is too little for the complexity.

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

Parameters1/5

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

All three parameters (website, offset, maxChars) have 0% schema description coverage, and the description supplies no meaning for any of them. The agent gets no hint about what website accepts, what offset paginates, or why maxChars defaults to 50000 — the description fails entirely to compensate 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 first sentence is essentially a restatement of the title ('Export crawl seed inventory') wrapped in a 'use this when' clause, adding no verb or scope detail beyond the name. It never distinguishes this export from sibling operations such as list_deep_crawl_seeds or export_deep_crawl_seed_attempts/errors, which an agent would have to disambiguate from the name alone.

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?

'Use this when the user asks to export crawl seed inventory' just paraphrases the tool name as its own trigger condition. There is no mention of when to prefer this over list_deep_crawl_seeds or the sibling export tools, and no prerequisites or exclusions are stated.

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