Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

usmagazine_sections

Retrieve all Us Weekly RSS section options, including slug, display name, and feed URL, to choose valid categories for headline feeds. No parameters required.

Instructions

Get Us Weekly RSS sections. Lists the 12 Us Weekly sections accepted by usmagazine-headlines, from celebrity-news and entertainment to reality-tv and royal-family. Each entry has a slug, display name and section feed url. Takes no parameters.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the load. It discloses that the call takes no parameters and that each entry has a `slug`, display `name` and feed `url`, which is real behavioral disclosure given the absence of an output schema. It does not discuss rate limits or caching, but for a static 12-item list that is a minor gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with what it returns, then who consumes it, then the entry shape. The example slugs are illustrative rather than filler, and nothing is redundant.

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 parameterless sibling-lookup tool with no output schema, the description states the count (12), the consumer (usmagazine-headlines), the examples, and the return fields. Nothing an agent needs to call it correctly is missing.

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?

Zero parameters, so the baseline is 4. The description reinforces this by stating 'Takes no parameters', which matches the empty schema and removes any doubt.

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 ('Get Us Weekly RSS sections') and immediately scopes it: it lists the 12 sections accepted by usmagazine-headlines. An agent can distinguish this from usmagazine_headlines, usmagazine_news and the other usmagazine tools without opening a schema.

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 names the consuming sibling ('sections accepted by `usmagazine-headlines`'), which tells the agent this is a discovery/lookup tool used to obtain valid section values. It gives clear context but no explicit when-not or alternative routing.

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