Prosp MCP Server

Create Lead List

create_lead_list

Create an empty lead list in Prosp named by campaign and signal type so agents can organize prospects for future outreach.

Instructions

Create an empty lead list.

Name it after the campaign and the signal type rather than the channel. "q3-saas-founders-job-post-trigger" is answerable in three months; "LinkedIn leads" is not.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes
`description`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 30, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the list is empty, but does not state auth requirements, duplicate-name behavior, side effects, or whether the list is immediately usable by import siblings.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first sentence, followed by a naming convention with concrete examples. The examples are useful, though the quoted illustrations add some length for a simple naming rule.

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

Completeness2/5

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

For a simple create tool with an output schema, the description still leaves significant gaps: no usage relative to import siblings and no semantics for the optional 'description' parameter. It adequately covers only the name parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It adds naming guidance for the 'name' parameter, but completely ignores the optional 'description' parameter, leaving one of two parameters undocumented in both schema and description.

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 verb and resource: 'Create an empty lead list.' The word 'empty' clearly distinguishes this from import tools and from list/get siblings. An agent can identify the operation without opening other definitions.

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

Usage Guidelines2/5

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

The description gives naming advice but no guidance on when to use this tool versus import_from_search, import_from_post, or import_leads. It also lacks any when-not or prerequisite information.

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