Skip to main content
Glama

Read a lead

get_lead
Read-onlyIdempotent

Read one lead: their details and consent, the lead magnet, their share links, the pages they read and a timeline of visits, downloads, shares and link clicks. Personal data, with the same rules as list_leads; needs the leads:read permission.

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": {
      "leadId": "<leadId>"
    },
    "name": "get_lead"
  }
}

Input Schema

NameRequiredDescriptionDefault
leadIdYesA lead's id from list_leads.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description still earns credit by flagging that the response contains personal data, that list_leads' handling rules apply, and that leads:read is required — facts the annotations do not convey.

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?

A single sentence, front-loaded with the verb and the returned resource set, with no filler. Every clause — contents, sensitivity, rules, permission — carries distinct operational information.

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 does the necessary work of enumerating return contents plus the permission and privacy context. The only soft spot is the unexplained "same rules as list_leads," which requires prior knowledge rather than stating the constraint directly.

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?

Schema coverage is 100% and the sole parameter leadId is already documented as "A lead's id from list_leads." The description adds no format, sourcing, or failure semantics for that id beyond what the schema states, so this sits at the baseline.

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?

"Read one lead" gives a specific verb and cardinality, and the colon-list enumerates exactly what comes back: details, consent, lead magnet, share links, pages read, and a timeline of visits/downloads/shares/clicks. The explicit "one lead" contrasts with list_leads, so the agent can distinguish them without opening either schema.

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?

The permission requirement (leads:read) and the pointer to list_leads' rules give real context for when this is callable. However, "the same rules as list_leads" is a deferred cross-reference with no restatement, and there is no explicit when-not or alternative-tool guidance such as get_lead_magnet for magnet-level 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