Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tomsguide_article

Retrieve a Tom's Guide article by canonical URL and return its title, description, authors, image, body paragraphs, and paywall status.

Instructions

Get Tom's Guide article content. Returns one Tom's Guide article by url, a canonical HTTPS tomsguide.com link such as tomsguide.com/<section>/<slug>. The response has the title, description, section, authors, publication and update times, image URL, body paragraphs and a paywalled flag. On some product reviews authors may be empty.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Tom's Guide article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the full burden and does well: it enumerates the returned fields (title, description, section, authors, timestamps, image, paragraphs), discloses a 'paywalled' flag, and warns that 'authors' may be empty on some product reviews. It omits any auth, rate-limit, or failure-mode context, keeping it short of 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 sentences, front-loaded with the purpose and input contract, followed by return contents and the caveat. No filler, though the return-field enumeration is dense in one clause.

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?

Since no output schema exists, the description is the only source of return-shape information, and it covers the key fields, the paywalled flag, and the empty-authors edge case. Missing details like body pagination or error behavior are minor for a single-URL fetch tool.

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 coverage is 100%, so the single 'url' param is already documented; the description goes beyond by giving the canonical form and an example path pattern ('tomsguide.com/<section>/<slug>'), which helps the agent construct a valid input rather than just name the field.

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 ('Get') and resource ('Tom's Guide article content'), and adds the scope detail 'Returns one ... article by url', which implicitly separates it from list-oriented siblings like tomsguide_headlines and tomsguide_news. It does not name those siblings explicitly, so it stops short of full differentiation.

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?

Usage is implied — you supply a canonical article URL to retrieve that article — but there is no statement of when to prefer this over tomsguide_headlines/news/sections for discovery, nor any exclusions or prerequisites beyond the URL format. Adequate but leaves routing to inference.

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