Skip to main content
Glama

List Lead Form Applicants

list_lead_form_applicants
Read-only

List applicants submitted to a lead form managed by the authenticated Nas.com user. Before offering this action or requesting its inputs, check business permissions. FREE businesses cannot use this tool, regardless of individual feature rows. Call check_business_tool_access before collecting inputs. Show any grace-period warning and verified resubscribe link before continuing, and never proceed when access is blocked.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "communityId": "<communityId>",
      "formId": "<formId>"
    },
    "name": "list_lead_form_applicants"
  }
}

Input Schema

NameRequiredDescriptionDefault
formIdYesLead form ID, from a Nas.com lead form listing.
pageNoNoPage number to return, starting at 1.
searchNoText to search for.
filtersNo
pageSizeNoNumber of results per page.
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / communityId / description
      Added value: +"Nas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one."
    • addedInput schema / properties / formId / description
      Added value: +"Lead form ID, from a Nas.com lead form listing."
    • addedInput schema / properties / pageNo / description
      Added value: +"Page number to return, starting at 1."
    • addedInput schema / properties / pageSize / description
      Added value: +"Number of results per page."
    • addedInput schema / properties / search / description
      Added value: +"Text to search for."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety is covered; the description adds real value beyond that with the paid-tier authorization requirement, the mandatory pre-check call, and the grace-period warning flow. It stops short of describing result shape or pagination behavior, which matters since there is no output schema.

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

Conciseness4/5

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

The purpose is front-loaded in sentence one and the gating rules follow in a logical order. There is mild redundancy between 'Before offering this action or requesting its inputs, check business permissions' and 'Call check_business_tool_access before collecting inputs,' but no sentence is wasted overall.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only paginated list with six parameters, no output schema, and an undocumented 'filters' parameter, the definition covers access gating thoroughly but says nothing about what is returned, how paging works, or what filters accepts. An agent can decide whether it may call the tool, but not fully predict the call's behavior.

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 83%, so the baseline is 3, and the description adds nothing about any parameter — not communityId provenance, not pageNo/pageSize semantics, and notably not the bare 'filters' parameter that the schema leaves undocumented. It neither compensates for the coverage gap nor overrides 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 first sentence names a specific verb and resource with scope: 'List applicants submitted to a lead form managed by the authenticated Nas.com user.' That is enough to distinguish it from singular lookups like get_lead_form_submission and from export_lead_form_applicants_csv, but it never names those siblings explicitly, so the differentiation is inferred rather than stated.

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?

It gives strong explicit when-not conditions: FREE businesses cannot use it regardless of feature rows, check_business_tool_access must run before collecting inputs, and the agent must never proceed when access is blocked. What is missing is routing guidance among the many sibling listing tools (e.g., when to prefer this over the CSV export or the analytics endpoint).

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