Skip to main content
Glama

List blog posts

list_blog_posts
Read-onlyIdempotent

List published ELD Hub blog posts (trucking, ELD, factoring, fuel cards, insurance, compliance). Returns slug, title, excerpt, category, cover image, and publish date.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_blog_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax posts to return (default 20).
categoryNoOptional category filter (e.g. 'compliance', 'factoring', 'fuel').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered; the description adds real value by enumerating the returned fields (slug, title, excerpt, category, cover image, publish date) and narrowing scope to *published* posts only. It omits ordering/pagination behavior, which would be the remaining behavioral gap.

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?

Two dense sentences: the first states scope and domain, the second states return shape. Nothing is repeated and the most decision-relevant information leads.

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?

With no output schema, the description usefully enumerates returned fields, and annotations cover the safety profile, so an agent has enough to invoke it correctly. Minor gap: no mention of default ordering or whether results are paginated beyond the limit cap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so limit (max 50, default 20) and category are already fully documented in the schema. The description's parenthetical topic list ('compliance', 'factoring', 'fuel cards') loosely hints at valid category values but does not formally tie them to the parameter. Baseline 3 applies.

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?

Specific verb ('List') plus a concrete resource ('published ELD Hub blog posts') and the topical domain, which cleanly separates it from sibling lookup tools like get_blog_post. It stops short of naming that sibling or explicitly contrasting list-vs-fetch, so 5 is not warranted.

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?

The word 'published' implies a browsing/discovery use case, but there is no explicit statement of when to call this versus get_blog_post for a single article, nor any prerequisite or exclusion. Usage must be inferred from the tool name and the word 'List'.

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