Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

getSmartList

Read-onlyIdempotent

Fetches a Follow Up Boss CRM smart list by ID to inspect its saved filters and list details.

Instructions

Get a smart list by ID

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": {
      "id": "<id>"
    },
    "name": "getSmartList"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSmart list ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered without the description. The description adds nothing beyond that: it does not say what a smart list is, what happens if the ID does not exist, or whether the response includes members/filters. With annotations carrying the safety burden, this remaining silence is a modest but real gap.

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?

A single short sentence, front-loaded with verb and resource, with zero filler. It is minimally sufficient rather than padded, though it is arguably too terse to earn top marks.

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 one-parameter read tool with full schema coverage and complete safety annotations, the definition is adequate to invoke correctly. It falls short on context an agent might want: no output schema exists, and the description never indicates what the returned smart list contains or how missing IDs are handled.

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 single id parameter is documented as "Smart list ID" with type number. The description's "by ID" merely restates the schema, so the baseline of 3 applies rather than anything higher.

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?

"Get a smart list by ID" states a specific verb (get) and resource (smart list) with its lookup key. The distinction from the sibling listSmartLists is implicit in the singular noun and "by ID" phrasing, though it is never stated explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of the sibling listSmartLists as the alternative for enumeration, and no prerequisites. The only implied guidance is that an ID is required, which the schema already enforces.

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

Deploy Server

Other Tools