Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ninetofivegoogle_article

Fetch a 9to5Google article from a canonical dated URL to return public metadata and readable body paragraphs, while skipping audio-first podcast archive slugs.

Instructions

Get a 9to5Google article. Returns public 9to5Google article metadata and readable body paragraphs from a canonical dated article URL. Audio-first podcast archive slugs are excluded from the sections list; podcast episodes that appear in the main feed can still be read when their page exposes metadata and paragraphs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical 9to5Google article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden, and it does disclose useful traits: returns public metadata plus readable paragraphs, and how podcast archive slugs vs main-feed podcast episodes are handled. It omits auth/rate-limit behavior, pagination, and failure modes, so it adds value but is not complete.

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?

Front-loaded with the purpose and return payload in the first sentence, with edge-case detail following. The podcast sentence is slightly dense but each clause conveys distinct behavior; no filler.

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?

No output schema or annotations exist, so the description must describe returns, and it does so adequately (metadata + body paragraphs) along with a scoping caveat. For a single-URL fetch tool this is near-complete, missing only error/permission behavior.

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?

One parameter with 100% schema coverage already documents the url field. The description reinforces the required input format ('canonical dated article URL'), adding the 'dated' nuance beyond the schema's 'Canonical 9to5Google article URL', which is meaningful for construction.

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

Purpose4/5

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

States a specific verb and resource ('Get a 9to5Google article') and specifies the output ('public article metadata and readable body paragraphs'). It does not explicitly name sibling tools like ninetofivegoogle_headlines or ninetofivegoogle_news, but the article-vs-feed distinction is clear from the name and payload description.

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

Usage Guidelines2/5

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

No guidance on when to use this versus the many sibling article/headline/news tools, and no statement about where the URL should come from (e.g. headlines results). The podcast note conveys a conditional edge case but not a use-vs-alternative rule.

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