Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

salon_headlines

Fetch headlines and story details for a chosen Salon section by slug, returning titles, URLs, summaries, publication times, authors, and images.

Instructions

Get Salon section headlines. Returns the latest Salon stories for one section. section is required and takes one of 32 slugs, including home, news-and-politics, politics, opinion, culture, science-and-health and technology. Each item has its title, URL, summary, publication time, author and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesSalon RSS section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.2/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 burden, and it does well for a read-only feed: it discloses that results are the "latest" stories and enumerates the per-item fields (title, URL, summary, publication time, author, image). It omits pagination, result-count, and rate-limit behavior, which keeps it from 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?

Three front-loaded sentences with no filler: purpose, parameter requirement, return fields. The inline list of seven sample slugs is slightly bulky given the schema already enumerates all 32, but it is not wasteful enough to penalize heavily.

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 single-parameter read tool with no annotations and no output schema, the description covers purpose, the required parameter, and the shape of returned items, which is exactly what the missing structured fields would otherwise have to carry.

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?

Schema description coverage is 100%, so baseline is 3; the description adds value by stating the parameter takes one of 32 slugs and surfacing common examples (home, news-and-politics, opinion, etc.) that help an agent pick a sensible value quickly, even though the enum already enumerates them.

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 ("Get") and resource ("Salon section headlines") with scope ("latest Salon stories for one section"). An agent can distinguish it from siblings like salon_sections, salon_article, and salon_news without opening any schema.

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?

Implies the use case (fetch a section's latest headlines) and states that `section` is required, but names no alternatives such as salon_news or salon_sections and gives no when-not guidance. Usage is inferable rather than stated.

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