Skip to main content
Glama

Eurekuh

Set a post's first comment

set_first_comment
Destructive

Give an existing post a first comment, or change its text or when it goes out, without recreating the post. Works until the post is out — and after, while a held comment ("after" / "views" / "likes") is still waiting. Fields left out keep their value; firstComment "" removes it (before the post is out only).

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": {
      "id": "<id>"
    },
    "name": "set_first_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe post id from create_post or list_posts.
firstCommentNo
organizationIdNoWhich organization to act in: an id from list_organizations. Leave out for this connection's default organization.
firstCommentTriggerNoWhen firstComment goes out. "now" (default): right after the post is live. "after": firstCommentThreshold minutes after it is live (e.g. 240 = 4 hours; at most 7 days). "views" / "likes": once the post has firstCommentThreshold of them — threads and instagram only, read every 5 minutes at first and less often as it ages; if it never gets there in 7 days the comment is not posted and get_post_status says why, unless firstCommentFallbackMinutes is set. A comment never fails the post.
firstCommentThresholdNoMinutes for "after", the count for "views" / "likes". Required unless the trigger is "now".
firstCommentFallbackMinutesNoOnly with "views" / "likes": whichever comes first. The comment goes out once the post has firstCommentThreshold of them, or this many minutes after it is live, even if the network gives no reading (e.g. threshold 5 + 300 = 5 likes or 5 hours). A whole number, 1 to 10080 (7 days). null removes it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the annotations (destructiveHint=true, idempotentHint=false) by spelling out partial-update semantics ('Fields left out keep their value'), the removal path (firstComment "" is destructive and only before the post is out), the post-publication window, and the failure mode ('A comment never fails the post'). It also cross-references get_post_status for post-mortem of a comment that never fired.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense but front-loaded: the core action and its lifetime constraint come first, the empty-string removal rule last. The nested parenthetical of trigger values is compressed, which is reasonable for a short description, though the single long sentence stacks several conditions.

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?

Covers lifecycle windows, partial-update behavior, and removal semantics; the trigger parameters are fully specified in the schema, and no output schema exists so return values need not be described. The remaining gap is the unstated relationship to update_post/create_post for an agent choosing among tools.

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 already 83% and documents the trigger enum and thresholds thoroughly, so baseline is 3. The description adds meaning the schema lacks, notably that firstComment "" removes the comment and that removal is only permitted pre-publication.

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?

States a specific verb+resource: set/change a post's first comment without recreating the post. The in-place-modification framing distinguishes it from create_post, but it never explicitly contrasts with the obvious sibling update_post, leaving the boundary to inference.

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?

Gives a concrete applicability window: 'Works until the post is out — and after, while a held comment is still waiting.' That is clear context on when the call is valid and when it is not, but no alternative tool is named for the cases where this call is not allowed.

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