Skip to main content
Glama
Sign In
mcp-lindoai

mcp-lindoai

Official
by lindoai
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
JavaScript
Remote

List Blog Posts

list_blogs
Read-only

Retrieve a list of all blog posts for a given website ID.

Instructions

List all blog posts on a website.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "website_id": "<website_id>"
    },
    "name": "list_blogs"
  }
}

Input Schema

NameRequiredDescriptionDefault
website_idYesThe website ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.17
  2. Removedv1.0.16
  3. First observedv1.0.14

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows the operation is safe. The description adds that it lists 'all' blog posts but does not mention pagination, ordering, or rate limits, which are beyond annotations but relevant.

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?

The description is a single, focused sentence. No unnecessary words or repetition. Well-structured and front-loaded.

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?

For a simple list tool with no output schema, the description adequately conveys purpose and scope. It could mention the return format (e.g., an array of blog objects), but the lack is not critical given the simplicity and sibling context.

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% for the single parameter 'website_id', so the description doesn't need to add meaning. The tool description does not elaborate further, but given full schema coverage, the baseline score is appropriate.

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?

The description 'List all blog posts on a website.' uses a specific verb 'list' and resource 'blog posts', clearly distinguishing it from siblings like 'get_blog' (single) and 'list_pages' (different resource).

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?

No explicit when-to-use or when-not-to-use guidance is provided. While the purpose is clear, the description lacks alternatives or exclusions, which would be helpful for an AI agent deciding between similar tools.

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