Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportingnews_author

Retrieve a Sporting News US author profile by slug or canonical URL to get their bio, photo, social links, and about 20 recent articles.

Instructions

Get a Sporting News author profile. Returns a Sporting News US author's profile, looked up by slug (for example anne-erickson) or canonical url; exactly one is required. The response has the name, bio, photo, social links and about 20 recent articles, each with title, URL, section, author, publication time and image. There is no pagination, and an unknown author returns not-found.

Input Schema

NameRequiredDescriptionDefault
urlNoCanonical sportingnews.com/us/author/<slug> URL; alternative to slug
slugNoAuthor slug, e.g. anne-erickson

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?

With no annotations the description carries the full burden, and it delivers: no pagination, unknown author returns not-found, and it enumerates what the response contains (name, bio, photo, social links, ~20 recent articles with fields). It omits auth/rate-limit behavior, keeping 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.

Conciseness5/5

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

Three sentences, front-loaded with purpose, then the lookup key constraint, then response/pagination behavior. Every sentence earns its place with no filler.

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?

Given there is no output schema, the description usefully describes the return shape and the no-pagination/not-found behaviors. Combined with the 100%-covered input schema, an agent has everything needed to call it correctly.

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 schema already documents both parameters and the baseline is 3. The description adds material value beyond the schema by asserting the mutual-exclusivity rule ('exactly one is required'), which the schema does not express since both params are optional.

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 a Sporting News author profile') and immediately scopes it to the US author resource distinguished from the sibling sportingnews_article/headlines/sections tools as well as other *_author tools. An agent can identify the tool without opening the 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?

Gives clear invocation context: exactly one of slug or url is required, with a concrete slug example ('anne-erickson'). It does not, however, state when to prefer this tool over sibling lookups (e.g. resolving an author from an article) or when not to use it, so it stops short of full 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