Skip to main content
Glama

fanaticscollect_newsroom

Read-only

List public Fanatics Collect newsroom posts with title, publication time, category, link and images when available. Page starts at 1. Use fanaticscollect_newsroom_filters to discover category and tag IDs and pass multiple IDs separated by hyphens. Sort newest first by default or choose oldest. An empty page is valid.

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

Input Schema

NameRequiredDescriptionDefault
pageNoOptional 1-based page. Defaults to 1.
tagsNoOptional tag ID or hyphen-separated tag IDs from fanaticscollect_newsroom_filters.
sort_byNoOptional sort order, newest or oldest. Defaults to newest.
categoryNoOptional category ID or hyphen-separated category IDs from fanaticscollect_newsroom_filters.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the read-only and open-world profile. The description adds operational behavior beyond them: 1-based paging, newest-first default with an oldest option, and the important note that an empty page is a valid result rather than an error. Missing only pagination limits or total-count behavior.

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?

Four short sentences, front-loaded with the resource and output fields, followed by paging, filtering, sorting, and edge-case notes. Slight redundancy with the schema on paging and sort defaults keeps it from a 5.

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?

For a simple paginated read-only list with an output schema, the description covers everything an agent needs: what is returned, how to page, how to build filters via the sibling tool, sort options, and empty-result semantics.

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%, so every parameter is already documented, including the hyphen-separated ID format and defaults. The description reinforces the same facts (page starts at 1, sort default) but adds no syntax or constraints beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ("List public Fanatics Collect newsroom posts") and names the fields returned (title, publication time, category, link, images). It is clearly distinct from the sibling fanaticscollect_newsroom_filters, which the description positions as the ID-discovery tool.

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?

Explains how to obtain filter values ("Use fanaticscollect_newsroom_filters to discover category and tag IDs") and how to combine them (hyphen-separated), plus the default sort order. It stops short of stating when not to use this tool versus other Fanatics Collect content endpoints, so a 4 rather than a 5.

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.