Skip to main content
Glama

Admin Substitute

by com.adminsubstitute

leads.list

Read-only

List leads and prospects. Returns name, phone, email, service type, status, priority, source, and timestamps. Supports filtering and cursor-based pagination. Tip: Use leads.create to add new leads, then leads.list to verify.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of leads to return. Defaults to 50, capped at 100.
cursorNoPagination cursor from previous response. Pass to get next page of results.
statusNoFilter by lead pipeline stage. Omit to return all statuses.
priorityNoFilter by priority level. Omit to return all priorities.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoTotal number of leads returned
leadsNoList of lead records
next_cursorNoCursor for next page. Null if no more results.

TDQS

A4.5/5.0
Behavior5/5

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

Consistent with readOnlyHint; describes returned fields and pagination support, adding valuable behavioral context beyond the annotation.

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 brief sentences and a tip, efficiently communicating purpose, returned data, and usage hint. No wasted words.

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?

Given the presence of an output schema and full parameter documentation, this description sufficiently covers filtering, pagination, and the specific data returned. No gaps.

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 baseline is 3; the description adds 'filtering and cursor-based pagination' context but does not deepen understanding beyond what schema descriptions provide.

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?

Clearly states 'List leads and prospects' and specifies returned fields. The tip mentioning leads.create distinguishes this read operation from its write sibling.

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?

Provides implicit usage guidance via tip linking leads.create to leads.list for verification. Does not explicitly state when not to use or name alternatives like clients.list.

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

All Admin Substitute toolsInspect
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

A3.8/5.0
Disambiguation4/5

Most tools have distinct resource+action naming (e.g., leads.create, jobs.list), but some overlap exists in analytics tools (dashboard, detailed, financials) and workflow automations (process_lead vs google_ads_pipeline). Descriptions clarify purposes, so slight confusion is possible but limited.

Naming Consistency5/5

All tools follow a consistent `domain.action` pattern (e.g., leads.create, billing.status). No mixing of camelCase or snake_case. Even complex names like lifecycle.assess or scaling.readiness_score adhere to the convention.

Tool Count1/5

95 tools is far beyond typical well-scoped servers (3-15). While the server aims to cover an entire business management platform, this volume is overwhelming for an agent, making selection and memory difficult.

Completeness5/5

The tool surface is exceptionally comprehensive, covering formation, hiring, compliance, funding, leads, quotes, jobs, invoicing, payments, marketing, analytics, integrations, webhooks, workflows, and more. Almost no obvious gaps in the lifecycle of running a trade business.

Resources