EvenLeads

Show my leads

get_my_leads

Read-onlyIdempotent

The leads EvenLeads has already found for the user: the public post, where it was posted, a 0-10 match score and why it matched, best matches first, across all campaigns unless a campaign id is given. Reads existing leads only and starts no search. The user must be signed in with EvenLeads.

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

Input Schema

Name	Required	Description
`limit`	No	Default 10.
`status`	No	Only leads with this status. Default: everything except not relevant.
`platform`	No	Only this platform, e.g. reddit, linkedin, x, facebook.
`min_score`	No	Minimum match score, 0-10.
`campaign_id`	No	Only this campaign (campaign id).

Output Schema

Name	Required	Description	Default
`leads`	No
`search`	No
`dashboard_url`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A4.3/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 the description's added value is the read-only scope boundary ("starts no search"), the default scope across all campaigns, and the authentication prerequisite. That is meaningful behavioral context beyond the annotations, though it says nothing about limits on result volume or what happens when no leads exist.

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 tight sentences: the resource and returned payload are front-loaded, then the scope boundary and auth requirement. No filler or repetition of schema text.

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?

An output schema exists, so return values need no further explanation, and the description still covers the essentials an agent needs: read-only behavior, default scope, ordering, and the sign-in prerequisite. Nothing critical to correct invocation 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 coverage is 100%, so each filter's meaning is already documented, and the description only adds the default campaign scope (all campaigns unless campaign_id is given). It does not clarify interaction between filters such as status and min_score, so the baseline of 3 is appropriate.

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 leads EvenLeads has already found for the user" names the exact resource, and the description enumerates what each lead contains (public post, platform, 0-10 match score, match rationale) plus ordering. It explicitly contrasts with a search action ("Reads existing leads only and starts no search"), so an agent can separate it from the search/fetch siblings without opening a schema.

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?

Clear usage context: use it to read already-found leads, in any campaign or scoped by campaign id, and it deliberately does not trigger a search. The condition for the alternative (run a search instead) is implied rather than naming the sibling tool, so it falls just short of explicit routing.

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

All EvenLeads 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.