simplepages

List captured leads

list_leads

Read-only

List the people who submitted a form, newest activity first. Scope to one page with pageId, to a whole website with siteId, or omit both for every lead in the workspace. Returns their contact details, which page they came from, and the fields they submitted. Spam that was already blocked is excluded by default.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum leads to return (default 50, max 100).
`offset`	No	How many to skip, for paging through a long list. Compare with `total` in the result to know whether more remain.
`pageId`	No	Only leads who submitted a form on this page (id from list_pages).
`search`	No	Match against name, email, or phone. Phone matching ignores formatting, so "(901) 555" finds "9015550001".
`siteId`	No	Only leads who submitted on any page of this website (id from list_sites). Ignored when pageId is given.
`workspace_id`	No	Which workspace to act in. Only meaningful when this connection can access more than one workspace: omit it and you get an error listing the available workspace ids (also available from list_sites) to choose from. On a single-workspace connection, omit it or pass that workspace's own id; a different id is rejected.
`includeBlocked`	No	Include contacts marked as spam. Off by default; turn it on only when reviewing what was blocked.

Output Schema

TableJSON Schema

Name	Required	Description
`count`	Yes	Leads in this response.
`leads`	Yes
`total`	Yes	Total matching the filters, ignoring paging.
`hasMore`	Yes	True when more leads match than were returned. Page with `offset`.
`scopeTruncated`	Yes	True when the page or site had more submissions than could be read in one pass, so some leads are missing from this list entirely. Paging will not recover them; narrow the scope instead.

TDQS

A4.6/5.0

Behavior4/5

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

The annotation readOnlyHint=true already indicates safe read operation. The description adds value by clarifying that spam is excluded by default, results are ordered newest first, and that the return includes contact details, page source, and submitted fields. It does not contradict annotations; it complements them nicely.

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 is one focused paragraph, efficiently conveying the use, scoping options, return content, and spam filter. Every sentence adds value, and the whole description is easy to scan using plain language.

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?

With an output schema present and the description covering read-only behavior, scoping, sorting, and return fields, the description is quite complete. It could mention pagination limits but the schema covers limit/offset. It adequately compensates for the tool's complexity and sibling context, hence a 4.

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

Parameters4/5

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

Schema coverage is 100%, so each parameter is well-documented. The description reinforces the meaning of pageId, siteId, and the omission of both, adding contextual explanation (e.g., siteId's precedence over pageId). It also adds insight into includeBlocked usage, which the schema notes but the description clarifies. Since the description adds beyond the schema, a 4 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 description clearly states the tool lists people who submitted a form (i.e., leads), and specifies the ordering (newest activity first) and the optional scoping (page, site, or all). This distinguishes it from sibling list tools by focusing on lead capture, not pages, scripts, or redirects.

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

Usage Guidelines5/5

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

The description explicitly states how to scope the query: use pageId for one page, siteId for a whole website, or omit both for all workspace leads. It also mentions the default exclusion of spam and suggests turning on includeBlocked only when reviewing blocked items. This provides clear context for when to use this tool and what parameters to choose.

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

All simplepages tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation5/5

Each tool has a distinct purpose, with clear differentiation between creating standalone pages vs. adding to sites, and separate analytics for pages, sites, and workspaces.

Naming Consistency4/5

Mostly follows verb_noun pattern, but uses both 'add' and 'create' for similar actions, and 'delete' vs 'remove' inconsistently.

Tool Count4/5

20 tools cover a broad range of functionality (pages, sites, redirects, scripts, webhooks, analytics, leads), which is reasonable but slightly on the higher side.

Completeness3/5

Covers CRUD for most entities, but lacks delete operations for pages, sites, scripts, and webhooks (except redirects), leaving notable gaps.

Resources

Need Help?