Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

thejournal_sections

List valid TheJournal.ie sections accepted by the headlines endpoint, including category and topic slugs, to find the correct section for headline queries.

Instructions

Get TheJournal.ie sections. Lists the 22 TheJournal.ie sections that the headlines endpoint accepts, verified 2026-09-25: nine category pages such as irish, politics and business, plus topic pages such as housing, courts, ukraine and gaza. Each entry has a slug, name and listing page url. Topic pages outside the site navigation are not served.

Input Schema

NameRequiredDescriptionDefault

No arguments

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 behavioral burden and does well: it discloses the exact count (22), a verification date, the categories of pages (nine category pages plus topic pages), the fields returned (slug, name, url), and a limitation ('Topic pages outside the site navigation are not served'). It omits auth/rate-limit details, but for a static list tool this is a minor gap.

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, then details the count, examples, output fields, and a limitation in four compact sentences. There is slight redundancy between 'Get TheJournal.ie sections' and 'Lists the 22 TheJournal.ie sections', but the text is otherwise efficient and structured.

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 no output schema and no annotations, the description is complete enough for an agent to invoke correctly: it explains the return format, the exact number of items, representative examples, and an important exclusion. Nothing critical for calling the 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?

The tool has zero parameters, so the baseline is 4. Schema coverage is 100% (vacuously), and the description adds useful output-field information (slug, name, url) but no parameter semantics are needed or missing.

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 TheJournal.ie sections. Lists the 22 TheJournal.ie sections'), and distinguishes the tool from the headlines endpoint by noting the sections are those 'the headlines endpoint accepts'. An agent can tell this is a static reference list, not a content fetcher.

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?

Provides clear context by saying the sections are those 'the headlines endpoint accepts', implying use for discovering valid section identifiers before calling thejournal_headlines. However, it does not explicitly instruct when to call this tool versus alternatives, nor does it state exclusions or a step-by-step usage pattern.

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