usagentleads-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| USAGENTLEADS_API_KEY | Yes | Your USAgentLeads API key, supplied through the local stdio server's environment (e.g. export USAGENTLEADS_API_KEY='your-key'). Store the key outside version control. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| coverageA | Get release date, catalog coverage and data limitations. No record credits spent. |
| count_recordsB | Count matching agents or brokerages. Searching spends no record credits. |
| preview_recordsA | Preview masked agents or brokerages. Searching spends no record credits. |
| credit_balanceA | Check the shared dashboard/API credit balance. |
| owned_recordsB | Read previously unlocked records. No record credits spent. Returns at most 100 records per page. |
| unlock_recordsB | SPENDS CREDITS: one per agent, two per brokerage. Obtain the user's approval for the exact selection and maxCredits before calling. Reuse the SAME UUID idempotencyKey and parameters on retries; never automatically create a new key after a timeout. Already-owned and contactless records cost zero. |
| create_exportB | Prepare an authenticated CSV download request for owned records. The download applies your suppression list and records an export audit. No credits spent; do not include your API key in a URL. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct stage of the lead-data workflow: metadata, counting, masked preview, balance, owned records, unlocking, and export. The no-credit tools (count_records, preview_records, coverage) are clearly differentiated by output type, and unlock_records is clearly separated from preview_records by cost and result.
All names use snake_case and are readable, but the pattern is not uniformly verb_noun: owned_records is adjective_noun, while coverage and credit_balance are noun phrases. The deviations are minor and still predictable within the domain.
Seven tools is well-scoped for a lead-data marketplace, with each tool earning its place by covering a distinct workflow step. There is no obvious redundancy or missing operational layer that would require more tools.
The surface covers the core lifecycle: coverage check, count, preview, credit balance, unlock, read owned records, and export. Minor gaps exist around suppression-list management and export history/status, but agents can work around these for the main purchase workflow.