Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gulfnews_author

Fetch a Gulf News author profile by slug or canonical author URL, returning name, job title, bio, and recent article titles, links, and summaries.

Instructions

Get a Gulf News author profile. Returns a Gulf News author profile, identified by slug (such as nathaniel-lacsina) or by a canonical gulfnews.com/author/<slug> url; provide exactly one. The response has the name, job title, bio and the single page of recent articles on the profile, each with title, url and sometimes a summary. Unknown authors return not found.

Input Schema

NameRequiredDescriptionDefault
urlNoCanonical gulfnews.com/author/<slug> URL; alternative to slug
slugNoAuthor slug, e.g. nathaniel-lacsina

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.4/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 does well: it enumerates the returned fields (name, job title, bio, one page of recent articles), notes the optional `summary`, and discloses error behavior ('Unknown authors return not found'). It omits auth/rate-limit 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?

Front-loaded with the purpose and efficient overall, but the opening two sentences are redundant ('Get a Gulf News author profile. Returns a Gulf News author profile...'), which costs a point.

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?

No output schema exists, yet the description specifies both accepted identifiers and the full return shape including the error case. Nothing an agent needs to invoke and interpret this tool is missing.

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 baseline is 3, but the description adds real value: a concrete slug example, the canonical URL shape, and the mutual-exclusivity rule ('provide exactly one') that the schema does not state.

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+resource ('Get a Gulf News author profile') and names the identifying keys. An agent can distinguish this from siblings like gulfnews_article, gulfnews_news, and gulfnews_sections 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 Guidelines4/5

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

Gives an explicit selection rule for the two parameters ('provide exactly one'), which is the key usage constraint. It does not, however, name or contrast any sibling tool, so it stops short of full when/when-not guidance.

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