Skip to main content
Glama

raumnebenan

Get article details by slugs

get_article_details_by_slugs
Read-onlyIdempotent

Fetches complete article details (full markdown body content, author, publishing dates, tags, and related article links) for an array of friendly-URL slugs (e.g. ["kano-model", "overview"]). Slugs can be obtained from list_articles, search_articles, get_stories_by_category, or get_articles_by_tag. If slugs are unknown, prefer finding them with search_articles or list_articles. Use get_article_details_by_uuids only when you have UUIDs instead of slugs.

Input Schema

NameRequiredDescriptionDefault
article_slugsYesA list of 1–10 article slugs

Output Schema

NameRequiredDescriptionDefault
dataYes
sourceYes
retrieved_atYes
copyright_holderYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / data / properties / next_page
      Added value: +{
      +  "description": "The next page number; absent on the last page.",
      +  "minimum": 2,
      +  "type": "integer"
      +}
    • addedOutput schema / properties / data / properties / page
      Added value: +{
      +  "description": "The returned page (1-based).",
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedOutput schema / properties / data / properties / per
      Added value: +{
      +  "description": "Items per page.",
      +  "minimum": 1,
      +  "type": "integer"
      +}
  2. Changed4 schema fields changed
    • addedInput schema / properties / article_slugs / items / minLength
      Added value: +1
    • addedInput schema / properties / article_slugs / minItems
      Added value: +1
    • addedInput schema / properties / article_slugs / uniqueItems
      Added value: +true
    • changedOutput schema / properties / data / properties / hint / description
      Previous value: -"Guidance for the agent when no articles were found."New value: +"Guidance for the agent when no articles were found or some requested identifiers could not be resolved."
  3. Changed9 schema fields changed
    • changedInput schema / properties / article_slugs / description
      Previous value: -"A list of article slugs"New value: +"A list of 1–10 article slugs"
    • addedInput schema / properties / article_slugs / items / maxLength
      Added value: +120
    • addedInput schema / properties / article_slugs / maxItems
      Added value: +10
    • removedOutput schema / properties / articles
      Removed value: -{
      -  "items": {
      -    "properties": {
      -      "article_slug": {
      -        "type": "string"
      -      },
      -      "article_uuid": {
      -        "type": "string"
      -      },
      -      "author": {
      -        "type": "string"
      -      },
      -      "body_markdown": {
      -        "type": "string"
      -      },
      -      "category": {
      -        "type": "string"
      -      },
      -      "copyright_holder": {
      -        "type": "string"
      -      },
      -      "is_part_of_story": {
      -        "type": "string"
      -      },
      -      "last_article_update": {
      -        "type": "string"
      -      },
      -      "original_publishing_date": {
      -        "type": "string"
      -      },
      -      "related_articles_by_friendly_url": {
      -        "items": {
      -          "type": "string"
      -        },
      -        "type": "array"
      -      },
      -      "source_url": {
      -        "type": "string"
      -      },
      -      "summary": {
      -        "type": "string"
      -      },
      -      "tags": {
      -        "items": {
      -          "type": "string"
      -        },
      -        "type": "array"
      -      },
      -      "title": {
      -        "type": "string"
      -      }
      -    },
      -    "required": [],
      -    "type": "object"
      -  },
      -  "type": "array"
      -}
    • addedOutput schema / properties / copyright_holder
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / data
      Added value: +{
      +  "properties": {
      +    "articles": {
      +      "description": "The list of articles.",
      +      "items": {
      +        "properties": {
      +          "article_slug": {
      +            "type": "string"
      +          },
      +          "article_uuid": {
      +            "format": "uuid",
      +            "type": "string"
      +          },
      +          "author": {
      +            "type": "string"
      +          },
      +          "body_markdown": {
      +            "type": "string"
      +          },
      +          "category": {
      +            "type": "string"
      +          },
      +          "copyright_holder": {
      +            "type": "string"
      +          },
      +          "is_part_of_story": {
      +            "type": "string"
      +          },
      +          "last_article_update": {
      +            "format": "date-time",
      +            "type": "string"
      +          },
      +          "original_publishing_date": {
      +            "format": "date-time",
      +            "type": "string"
      +          },
      +          "related_articles_by_friendly_url": {
      +            "description": "Slugs of related articles.",
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "source_url": {
      +            "format": "uri",
      +            "type": "string"
      +          },
      +          "summary": {
      +            "type": "string"
      +          },
      +          "tags": {
      +            "description": "Tags for the article.",
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "title": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "source_url",
      +          "copyright_holder",
      +          "original_publishing_date",
      +          "last_article_update",
      +          "title",
      +          "summary",
      +          "article_slug",
      +          "related_articles_by_friendly_url"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "hint": {
      +      "description": "Guidance for the agent when no articles were found.",
      +      "type": "string"
      +    },
      +    "invalid": {
      +      "description": "List of requested identifiers that were invalid.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "not_found": {
      +      "description": "List of requested identifiers that were not found.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "total": {
      +      "description": "The total number of articles.",
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "unavailable": {
      +      "description": "List of requested identifiers that could not be fetched due to upstream issues.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "total",
      +    "articles"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / retrieved_at
      Added value: +{
      +  "format": "date-time",
      +  "type": "string"
      +}
    • addedOutput schema / properties / source
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[]New value: +[
      +  "source",
      +  "copyright_holder",
      +  "retrieved_at",
      +  "data"
      +]
  4. First observed

TDQS

A4.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed-world profile, so the safety burden is lifted. The description adds that the response is 'complete' with 'full markdown body content', hinting at a large payload, but says nothing about behavior on unknown/invalid slugs or per-slug failure handling. Adequate but not rich beyond the structured hints.

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, zero filler, and front-loaded: what is returned comes first, provenance and disambiguation follow. Every sentence carries routing or payload information.

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?

An output schema exists, so return values need not be explained; the description still names the high-value fields an agent would care about. Combined with the sibling routing, an agent has everything needed to select and call this tool 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 baseline is 3, but the description adds genuine meaning: concrete slug examples (["kano-model", "overview"]) clarifying format, and the provenance of valid slugs via four sibling tools. It does not restate the 1–10 bound, which the schema already carries.

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?

Specific verb (fetches) plus resource (complete article details) with an explicit enumeration of payload contents (markdown body, author, dates, tags, related links). It also states the input shape (array of friendly-URL slugs) and names the sibling it is not (get_article_details_by_uuids), so an agent can distinguish it without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly routes the agent: slugs come from list_articles, search_articles, get_stories_by_category, or get_articles_by_tag; if unknown, prefer search_articles or list_articles; use get_article_details_by_uuids only when UUIDs are held. Both the when and the alternatives are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources