Skip to main content
Glama
Sign In

Getlead

by ad.getle
OverviewDiscussionsAdmin

Export a list as CSV

export_list_csv
Read-onlyIdempotent

Return list contents as CSV text, at most 1000 rows. Use it to hand the data to the user or another tool; do not use it to page through a large list.

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": {
      "list_id": "<list_id>"
    },
    "name": "export_list_csv"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows, max 1000
list_idYesList id
email_statusNoOnly export leads with this status

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds the 1000-row limit and the intended handoff use, which complement the annotations without repeating them. It doesn't contradict any annotation.

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?

Two sentences with no wasted words. The main action and constraint are front-loaded, followed by a clear usage directive. Every clause earns its place.

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 simple list-export tool, the description plus schema and annotations cover what an agent needs: return format (CSV text), row limit, and when to use it. No output schema exists, but the return type is explicitly stated, so nothing critical 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?

Schema description coverage is 100%, so the schema already documents list_id, limit, and email_status. The description's 'at most 1000 rows' is directly derived from the limit maximum and adds no new parameter-specific meaning, so baseline 3 applies.

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?

The description uses a specific verb-resource pair ('Return list contents as CSV text') and states the format and row cap. It implicitly distinguishes from paging tools like get_list_leads by warning against using it for large-list paging, so an agent can tell it apart.

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

Usage Guidelines5/5

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

Explicitly says when to use it ('hand the data to the user or another tool') and when not to ('do not use it to page through a large list'). This gives clear decision rules for selecting this tool over siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Getlead toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources