Skip to main content
Glama
Sign In
kadenzo-mcp

kadenzo-mcp

by Kadenzo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

list_posts

Retrieve your social posts in reverse chronological order, with optional status filtering and pagination to control results.

Instructions

List your posts, newest first. Optionally filter by status (comma-separated, e.g. "pending,posted") and paginate with limit (1-100) and offset.

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_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
statusNoComma-separated statuses, or omit for all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.2

TDQS

A4.4/5.0
Behavior4/5

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

The description discloses ordering behavior (newest first) and parameter usage (comma-separated status). Without annotations, it does not explicitly state read-only or auth needs, but for a list tool this is sufficient.

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?

Single sentence with 20 words, efficiently conveying purpose and optional parameters with no wasted words.

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?

The tool has no output schema but the description implies a list of posts. It covers ordering, filtering, and pagination. Could specify it returns the user's own posts, but context is adequate.

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 low (33%), but the description adds meaning to all parameters: limit (1-100), offset (pagination), status (comma-separated). This compensates for missing schema descriptions.

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 clearly states 'List your posts, newest first,' specifying the verb (list) and resource (posts) with ordering. It distinguishes from siblings like get_post (single post) and get_post_analytics.

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?

The description explains optional filtering by status and pagination with limit and offset, providing clear context for use. It does not explicitly state when not to use or mention alternatives, but the sibling tools offer differentiation.

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