Skip to main content
Glama
Sign In
kadenzo-mcp

kadenzo-mcp

by Kadenzo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

post_comment

Post a comment or reply to a post on Instagram, Facebook, or LinkedIn by providing account ID, target post ID, and text.

Instructions

Post a comment/reply to one of your posts. account_id from list_accounts; target_id is the platform post/media/comment id to comment on. Supported: instagram, facebook, linkedin.

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": {
      "account_id": "<account_id>",
      "target_id": "<target_id>",
      "text": "<text>"
    },
    "name": "post_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
target_idYesThe platform post/media/comment id to comment on.
account_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.2

TDQS

A4.1/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. Mentions it posts a comment/reply but does not disclose authentication requirements, rate limits, error handling, or potential consequences (e.g., irreversibility).

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?

Extremely concise: one sentence with essential information, no unnecessary words. Front-loaded with core action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers basic purpose and parameters but lacks return value information (no output schema) and error handling details. For a creation tool, it is adequate but could be more informative.

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?

Adds meaningful context beyond schema: account_id sourced from list_accounts, target_id explained as platform post/media/comment id. However, text parameter lacks any extra description (character limits, formatting). Schema coverage is low (33%), but description partially compensates.

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?

Description clearly states the action: posting a comment/reply to one of your posts. It lists supported platforms (Instagram, Facebook, LinkedIn) and distinguishes from sibling tools (no other comment tool exists).

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 guidance on parameter sources (account_id from list_accounts) and target_id definition. Lack of explicit when-to-use vs alternatives, but no competing sibling for commenting.

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