Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

globalnews_author

Retrieve a Global News author profile by URL to access their name, biography, image, and recent articles.

Instructions

Get a Global News author profile. Returns a Global News author profile by url, a canonical https://globalnews.ca/author/<slug>/ link. The response has the author's name, biography, image_url and a list of recent articles. title, image_url and biography appear only if the author page shows them, and each article's published_at is relative text such as 2 hours or Sep 16, not a timestamp.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Global News author 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, the description carries the full behavioral burden and does add useful context: it discloses the returned fields, conditional presence of title/image_url/biography, and that article published_at values are relative text rather than timestamps. It does not cover error behavior, rate limits, or pagination for the recent-articles list, so it is strong but 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?

The description is appropriately sized and front-loads the core action and return format. The opening “Get a Global News author profile” is slightly redundant with the following sentence, and mentioning title despite not listing it in the main response fields is a minor structural wrinkle.

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?

Because there is no output schema, the description must explain return values, and it does: name, biography, image_url, recent articles, conditional fields, and relative published_at text. It is nearly complete for a simple one-parameter profile tool, though article-list size or pagination is unstated.

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?

The schema already documents url at 100% coverage, but the description adds format detail by specifying the canonical https://globalnews.ca/author/<slug>/ pattern. That is meaningful beyond the schema’s “Canonical Global News author URL” text.

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?

The description uses a specific verb and resource — “Get a Global News author profile” — and states that it returns a profile by URL. It is clear on its own, though it does not explicitly distinguish itself from sibling author-profile tools or from article tools.

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 only implied: call it with a canonical author URL to retrieve that author’s profile. There is no explicit when-to-use guidance, no exclusions, and no comparison to alternatives such as globalnews_article or globalnews_news.

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