Skip to main content
Glama

67Leads

Export leads (spends credits)

export_leads

Take the leads in a quote and return them as CSV text. Spends credits exactly like the web export, and each lead is charged once ever. Never call without the user's explicit confirmation of the quoted price.

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": {
      "quote_token": "<quote_token>"
    },
    "name": "export_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
quote_tokenYesFrom quote_export.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only tell the agent this is a non-read-only, non-destructive, non-idempotent call; the description adds the material facts the annotations omit: it consumes credits, it mirrors web-export billing, and each lead is charged once ever. The confirmation requirement is exactly the kind of behavioral constraint an agent cannot infer from structured fields. Minor tension with idempotentHint=false (repeat calls still won't double-bill), but not a contradiction.

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?

Three short sentences: what it does, what it costs, and the gate condition, with the cost warning placed before the confirmation rule. No filler and nothing buried.

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

Completeness5/5

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

For a one-parameter, no-output-schema tool, the description covers input provenance (implicitly), return format (CSV text), cost behavior, and the safety gate. Nothing an agent needs to call this correctly is missing.

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?

With a single parameter at 100% schema coverage, the baseline is 3; the schema already says quote_token comes from quote_export. The description adds only indirect framing ("the leads in a quote"), not format, validity, or expiry semantics for the token.

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?

"Take the leads in a quote and return them as CSV text" gives a specific verb (take/return), a specific resource (leads in a quote), and the output format (CSV). That is enough to tell it apart from search_leads or count_leads, though it never names the sibling it pairs with (quote_export, which the schema points to).

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?

It states a hard precondition: never call without the user's explicit confirmation of the quoted price, which is a real when-not-to-use rule. It does not name an alternative path (e.g., previewing via quote_export or get_sample instead of spending credits), so the routing guidance is one-sided.

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