Skip to main content
Glama
LeadFlow MCP

LeadFlow MCP

by kfairy9999

Export leads CSV

export_leads_csv
Read-onlyIdempotent

Export leads to CSV text for spreadsheet import, with formula-injection protection, escaped quotes/newlines, a 5,000-row cap, truncation indicator, and money values in integer cents.

Instructions

Export leads as CSV text. Cells that start with =, +, -, or @ are prefixed with an apostrophe so a spreadsheet will not treat them as formulas. Quotes and newlines are escaped. The export caps at 5000 rows and sets truncated when that happens. Money is integer cents.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "export_leads_csv"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfNo
stageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior5/5

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

Beyond the readOnly, idempotent, non-destructive annotations, the description discloses CSV formula-injection mitigation, quote and newline escaping, a 5000-row cap, the truncated signal, and integer-cents money formatting. These are operational details an agent cannot obtain from the annotations or schema.

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?

The description uses five short sentences, front-loads the purpose, then covers injection safety, escaping, row limits, and money representation. Every sentence adds useful information with no filler.

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

Completeness3/5

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

The description explains the return format and export limits even though there is no output schema. However, it omits any explanation of the two input parameters, especially asOf and stage, leaving the agent unsure how filtering affects the export.

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?

Neither input parameter is mentioned: asOf has no format or meaning, and stage is not tied to export behavior. With 0% schema description coverage, the description needed to compensate for the undocumented parameters and does not.

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?

The description states a specific action, 'Export leads,' and the output form, 'CSV text,' so the resource and serialization are unambiguous. It does not explicitly contrast with sibling tools such as search_leads, so it stops short of full sibling differentiation.

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 phrase 'Export leads as CSV text' implies that this tool is for spreadsheet-oriented export rather than browsing or editing leads. However, there is no explicit when-to-use or when-not-to-use guidance and no alternative is named.

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