sprkly-mcp

List leads

sprkly_list_leads

Read-only

People an automation answered in the last days (default 7), newest first: their handle, the keyword they used, the post they asked under, and the email they gave, if any. Filter by account, keyword or has_email. opted_out is true when the person sent STOP; never contact them. Never message a lead unless the user asks. Needs inbox access.

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": "sprkly_list_leads"
  }
}

Input Schema

Name	Required	Description
`days`	No	How many days back. Default 7, up to 90.
`limit`	No	How many people. Default 50, up to 200.
`keyword`	No	Only people who used this keyword, like LINK.
`has_email`	No	true: only people who gave an email. false: only people who did not.
`profile_id`	No	Only this connected account.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds meaningful behavior on top: result ordering ('newest first'), the default time window, what a lead row contains, the `opted_out` STOP semantics, and the inbox-access prerequisite. That is exactly the kind of context annotations cannot express.

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 tightly packed sentences, front-loaded with what the tool returns, followed by filters and then safety caveats. No filler, and the ordering of information matches how an agent would need it.

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?

With no output schema, the description correctly takes on the burden of describing the returned fields. Combined with the ordering, default window, auth prerequisite, and consent caveat, an agent has everything needed to call this read-only listing tool correctly.

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 all five parameters with defaults and bounds. The description reinforces the 7-day default and lists the filter axes (account, keyword, has_email), but adds no syntax or edge-case detail beyond what the schema states, so the 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?

States a specific resource and scope: 'People an automation answered in the last `days` (default 7)', then enumerates the returned fields (handle, keyword, post, email). This precisely defines 'leads' as automation-responders, which distinguishes it from adjacent siblings like sprkly_get_audience and sprkly_list_inbox_threads without needing to name them.

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?

Gives clear operational context: it needs inbox access, and it warns never to message a lead unless the user asks and never to contact opted-out people. It also notes the filterable dimensions. It stops short of naming an alternative tool for related needs (e.g. when to prefer inbox threads instead), so it is clear context without explicit exclusions.

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

All sprkly-mcp tools Inspect

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

Need Help?