Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

listTimeframes

Read-onlyIdempotent

Retrieve lead time-to-buy timeframe options from Follow Up Boss, with cursor paging and limit/offset controls for browsing up to 100 results per call.

Instructions

List timeframes (lead time-to-buy options). Returns up to 100 per call; if _metadata.next is set, call again with next.

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

Input Schema

NameRequiredDescriptionDefault
nextNoCursor from _metadata.next of the previous call for the next page.
limitNoResults per call, max 100. Server sends 100 when omitted (FUB's own default is 10).
offsetNoRows to skip before returning results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.0
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Results per call, max 100. Server sends 100 when omitted (FUB's own default is 10).",
      +  "type": "integer"
      +}
    • addedInput schema / properties / next
      Added value: +{
      +  "description": "Cursor from _metadata.next of the previous call for the next page.",
      +  "type": "string"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Rows to skip before returning results.",
      +  "type": "integer"
      +}
  2. First observedv1.1.1

TDQS

A3.7/5.0
Behavior4/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 covered. The description adds real behavioral value beyond that: it discloses the server-imposed page cap and the exact continuation contract via _metadata.next. It omits ordering, error behavior, and total-count semantics, keeping it short of a 5.

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?

Two short clauses, front-loaded with the identification of the resource before the pagination mechanics. No filler sentences. The only minor redundancy is repeating the 100-item cap that the limit parameter already documents.

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?

A simple read-only list tool with three optional parameters, rich annotations, and no output schema; the description covers what it returns and how to page through results. Nothing essential for correct invocation is missing, though return-field structure beyond _metadata.next is left implicit.

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 100% and the schema descriptions are unusually good, including the note that the server sends 100 when limit is omitted versus FUB's own default of 10. The description's 'returns up to 100 per call' and cursor mention largely restate the schema, so it only adds the connection between the next parameter and the _metadata.next response field.

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?

Description states a specific verb+resource ('List timeframes') and clarifies the domain term with a parenthetical ('lead time-to-buy options'), which is genuinely necessary since 'timeframes' is ambiguous in a CRM context. It does not distinguish itself from siblings, but the resource is unique enough among the many list* tools that selection is unambiguous.

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 description gives procedural guidance for pagination ('if _metadata.next is set, call again with next') but never says when this tool is the right choice versus alternatives, nor any prerequisites or exclusions. Usage is only implied by the tool being a plain reference-data lister.

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