USCardForum MCP Server

get_all_topic_posts

Fetch all posts from a USCardForum topic with automatic pagination, allowing retrieval of entire discussions or specific post ranges.

Instructions

Fetch all posts from a topic with automatic pagination.

Args:
    topic_id: The numeric topic ID
    include_raw: Include markdown source (default: False)
    start_post_number: First post to fetch (default: 1)
    end_post_number: Last post to fetch (optional, fetches to end if not set)
    max_posts: Maximum number of posts to return (optional safety limit)

This automatically handles pagination to fetch multiple batches.

IMPORTANT: For topics with many posts (>100), use max_posts to limit
the response size. You can always fetch more with start_post_number.

Use cases:
- Fetch entire small topic: get_all_topic_posts(topic_id=123)
- Fetch first 50 posts: get_all_topic_posts(topic_id=123, max_posts=50)
- Fetch posts 51-100: get_all_topic_posts(topic_id=123, start_post_number=51, max_posts=50)
- Fetch specific range: get_all_topic_posts(topic_id=123, start=10, end=30)

Returns the same Post structure as get_topic_posts but for all matching posts.

Pro tip: Use get_topic_info first to check post_count before deciding
whether to fetch all or paginate manually.

Input Schema

TableJSON Schema

Name	Required	Description
`topic_id`	Yes	The numeric topic ID
`include_raw`	No	Include markdown source (default: False)
`start_post_number`	No	First post to fetch (default: 1)
`end_post_number`	No	Last post to fetch (optional, fetches to end if not set)
`max_posts`	No	Maximum number of posts to return (optional safety limit)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedDec 30, 2025

TDQS

A4.6/5.0

Behavior4/5

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It effectively describes key behaviors: automatic pagination, safety limits with max_posts, and the ability to fetch specific ranges. It mentions the return structure ('Returns the same Post structure as get_topic_posts') and provides practical tips. However, it doesn't cover potential errors, rate limits, or authentication needs, which keeps it from a perfect score.

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 description is well-structured with clear sections (purpose, args, important notes, use cases, returns, pro tip). It is front-loaded with the core purpose and includes only relevant details. However, it is slightly verbose with repetitive examples, which prevents a perfect score, but every sentence adds value to guide usage.

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

Completeness5/5

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

Given the tool's complexity (5 parameters, automatic pagination) and the presence of an output schema (which handles return values), the description is complete. It covers purpose, parameters, usage guidelines, behavioral traits, and integration with sibling tools. The output schema means the description doesn't need to explain return values in detail, and it effectively addresses all other aspects needed for correct tool selection and invocation.

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?

The schema description coverage is 100%, so the baseline is 3. The description adds significant value beyond the schema by explaining parameter interactions and use cases in the 'Args' section and examples. It clarifies how parameters like start_post_number, end_post_number, and max_posts work together, and provides default behaviors. This enhances understanding beyond the schema's basic descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Fetch all posts from a topic with automatic pagination.' It specifies the verb ('fetch'), resource ('posts from a topic'), and key behavior ('automatic pagination'). It distinguishes from sibling 'get_topic_posts' by emphasizing the automatic pagination for fetching all posts rather than manual pagination.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool versus alternatives. It includes an 'IMPORTANT' note for topics with many posts (>100) to use max_posts, advises using 'get_topic_info first to check post_count before deciding whether to fetch all or paginate manually,' and gives specific use cases with examples. It clearly differentiates from 'get_topic_posts' by handling pagination automatically.

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