Skip to main content
Glama

ADS Beast

get_new_leads

Read-only

A page of leads with contact details, form answers and attribution (UTM, click ids, platform form, lead and campaign ids). Pass updated_since (ISO-8601, your last sync) to get only new or changed leads. Reply: {count, leads, has_more, next_offset, offset, limit}; page with next_offset while has_more.

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_new_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size. Clamped into 1..5000 before the request. A page is also cut to fit the response size limit; when the reply has has_more = true, call again with offset = next_offset.
sinceNoISO-8601 timestamp. Returns leads created at or after it, ignoring later edits to older leads.
stageNoRestrict to one pipeline stage. One of: new, contacted, qualified, proposal_sent, negotiation, won, lost.
offsetNoPagination offset. Use next_offset from the previous page.
sourceNoWhere the lead came from, for example 'meta_lead_form' for Meta instant forms or 'public_form' for a website form.
client_idNoRestrict to one client. A client of another organization answers 404.
updated_sinceNoISO-8601 timestamp, for example 2026-06-13T18:00:00Z. Returns leads updated at or after it, which is the last-sync value for incremental pulls.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint, so the safety profile is covered by structured data. The description adds real behavioral context the annotations lack — incremental sync semantics via updated_since and the pagination loop driven by has_more/next_offset. It does not mention rate limits, permissions, or the response-size clamping that the schema references, so it is solid but not rich.

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?

Three dense sentences with zero waste: what comes back, how to do an incremental pull, and exactly how to page. The most important operational facts are front-loaded and the response shape is given inline rather than buried.

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

Completeness4/5

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

No output schema exists, and the description compensates by naming the reply envelope (count, leads, has_more, next_offset, offset, limit) and the paging rule. All parameters are optional and schema-documented, so what remains unsaid — the field-level shape of each lead, or the default page size behavior — is minor for a read-only list endpoint.

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 full baseline of 3 applies; all seven parameters including the stage enum are documented in the schema. The description repeats the updated_since last-sync behavior already spelled out in the schema and never mentions the distinct 'since' (created-at) parameter, so it adds little meaning beyond structured fields.

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?

States a specific resource with contents: a page of leads with contact details, form answers and attribution fields. It does not explicitly contrast with the sibling get_lead (single lead) or leads_quality_diagnose, so the agent must infer that this is the paginated list endpoint from 'a page of leads' and the pagination language.

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 guidance: pass updated_since with your last sync value to get only new or changed leads, and page with next_offset while has_more is true. It does not name an alternative tool or state when not to use this one, which keeps it below a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.