Skip to main content
Glama

Search Leads Tool

search-leads
Read-only

Searches authorized workspace leads with bounded contact, source, status, and service-interest fields; notes and estimated values are excluded. Use to search leads in the connected business. Returns query, count, leads, scope.

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": "search-leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of leads to return.
queryNoName, email, phone, source, or service interest.
sourceNoOptional exact lead source.
statusNoOptional lead status.
urgencyNoOptional urgency: low, medium, or high.
customer_idNoRestrict results to a customer ID.

Output Schema

NameRequiredDescriptionDefault
countYesCount for the returned result.
leadsYesBounded leads records returned by this tool.
queryYesQuery used or returned by this tool.
scopeYesAuthorization scope of this result; data remains restricted to the connected business.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "count": {
      +      "description": "Count for the returned result.",
      +      "type": "integer"
      +    },
      +    "leads": {
      +      "description": "Bounded leads records returned by this tool.",
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "query": {
      +      "description": "Query used or returned by this tool.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "scope": {
      +      "description": "Authorization scope of this result; data remains restricted to the connected business.",
      +      "enum": [
      +        "connection_business"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "query",
      +    "count",
      +    "leads",
      +    "scope"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuine value by disclosing data boundaries (notes and estimated values excluded) and authorization scoping, but says nothing about matching behavior (exact vs partial), pagination, or truncation at the limit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is dense and front-loaded, but the second sentence ('Use to search leads in the connected business') largely restates the first, and the return-field list duplicates what the output schema already provides. Trimming those would leave a tighter definition.

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?

Parameters are fully self-documented and an output schema exists, so the description only needs to supply scope and boundaries — which it does via the authorized-workspace and excluded-fields clauses. The main residual gap is matching/ordering behavior for results, which an agent might want before relying on the output.

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 description coverage is 100%, so the schema carries parameter meaning and the baseline is 3. The description slightly reinforces it by naming the searchable field families (contact, source, status, service interest), which confirms what 'query' spans, though it adds no syntax or format detail beyond the schema.

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?

The description uses a specific verb+resource ('Searches ... leads') and adds scope detail: authorized workspace leads, with notes and estimated values excluded. It does not distinguish itself from siblings like get-lead or search-customers, so it stops short of the top mark.

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

Usage Guidelines3/5

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

'Use to search leads in the connected business' implies the usage context but gives no explicit when-to-use vs when-not guidance and names no alternative (e.g., get-lead for a single lead, search-customers for people lookup). The intent is inferable but not routed.

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.

Resources