Skip to main content
Glama

ADS Beast

list_lead_forms

Read-only

Return the lead forms recorded for this organization, which maps the form ids and source keys that appear on a lead to readable form names.

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": "list_lead_forms"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoForms per page, newest first. Each form carries its questions, so keep pages small.
offsetNoForms to skip; use next_offset from the previous page.
platformNoRestrict to one platform, for example meta.
client_idNoRestrict to one client.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that results are organization-scoped and map IDs/source keys to readable names, but it does not add behavioral details such as rate limits, permission requirements, or return ordering beyond what the schema provides.

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 a single sentence that is front-loaded with the resource and its purpose. Every clause contributes to clarifying what is returned and how the values are useful, with no unnecessary wording.

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?

For a simple read-only list tool with fully described parameters and no output schema, the description is largely complete: it states the organization scope and the conceptual mapping of form IDs/source keys to readable names. It could mention pagination behavior for the returned list, but the schema already covers that for inputs.

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%, and the schema already documents pagination via limit/offset, the platform filter, and client_id. The description adds no parameter-specific meaning beyond the schema, so the baseline of 3 is appropriate.

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 states a specific verb and resource: return the lead forms recorded for this organization. The second clause clarifies that this is a lookup/mapping resource, which distinguishes it from lead-mutation siblings such as update_lead or move_lead_stage, though it does not explicitly name alternatives.

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?

The mapping clause implies the tool is used to resolve form IDs and source keys into readable names, which gives some usage context. However, it does not state when to use this versus other list tools or when not to use it.

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.