Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

fanaticscollect_newsroom

List public Fanatics Collect newsroom posts with title, publication time, category, link and images; filter by category or tag IDs, sort newest or oldest, and page through results.

Instructions

Fanatics Collect newsroom article metadata. 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
pageNo1-based page number
tagsNoTag ID or hyphen-separated IDs
sort_byNoPublication sort order
categoryNoCategory ID or hyphen-separated IDs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it declares read-only public scope, the newest-first default with an oldest alternative, 1-based paging, that images are only present 'when available', and that an empty page is a valid result rather than an error. It omits auth/rate-limit behavior and whether total counts are returned, which keeps it below 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?

Four short sentences, front-loaded with purpose then paging, filtering, and sorting; there is little waste, though the paging and hyphen conventions partially duplicate the schema rather than adding new information.

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?

For a four-param, no-required-param list tool with no output schema, the description covers the returned fields, optionality of images, default ordering, and empty-result semantics, leaving an agent able to call it correctly. Missing detail on result limits or paging depth is minor.

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 already states '1-based page number', 'Tag ID or hyphen-separated IDs', and the sort enum, so the description mostly restates structured data. The only genuine addition is the explicit newest-first default for sort_by, making the baseline 3 appropriate.

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 opens with a specific verb and resource ('List public Fanatics Collect newsroom posts') and enumerates the returned fields (title, publication time, category, link, images), which separates it cleanly from fanaticscollect_newsroom_filters, the sibling it names explicitly.

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 routes the agent to fanaticscollect_newsroom_filters for discovering category and tag IDs and explains the hyphen-separated multi-ID convention, plus the default sort and 1-based paging. It stops short of stating when this tool is not appropriate, so it is clear context without explicit exclusions.

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