Conecto

Answer for the owner of a post

social_confirm_post

The owner's answer from your chat to a TikTok post waiting for them, after you showed them what social_post_check gave. post true sends it with their choices, now or at its time; post false drops it and refunds it. who_can_see is the value they picked from who_can_see; the allow_* switches and the disclosure stay off unless they said yes; caption and title only when they changed them. owner_said is their reply in their own words, kept as the record of their answer. Never choose for them: TikTok requires that they do. Free: social_post paid for it. Free.

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": {
      "check_id": "<check_id>",
      "post": "<post>",
      "owner_said": "<owner_said>"
    },
    "name": "social_confirm_post"
  }
}

Input Schema

Name	Required	Description
`post`	Yes	true: post it with their choices; false: they said no.
`title`	No	Photo posts only.
`caption`	No
`check_id`	Yes	A check_id from social_post's waiting_for_owner.
`allow_duet`	No	Videos only.
`owner_said`	Yes	The owner's reply, in their own words.
`who_can_see`	No
`allow_stitch`	No	Videos only.
`allow_comments`	No
`branded_content`	No
`promotes_own_brand`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Beyond the annotations, the description discloses important behavior: post true sends now or at its scheduled time, post false drops and refunds, allow_* switches and disclosure default to off unless the owner approved, and caption/title change only when edited. It does not cover permission needs, failure modes, or response behavior, but annotation coverage lowers the burden.

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

Conciseness3/5

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

The core behavioral guidance is front-loaded and useful, but the paragraph contains waste and circular wording, especially 'who_can_see is the value they picked from who_can_see' and the redundant closing 'Free: social_post paid for it. Free.' These reduce precision without adding meaning.

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 an 11-parameter mutation tool with no output schema, the description covers the essential decision semantics, default behavior, and the requirement to preserve owner choice. It is still missing return/error details and does not fully document every parameter, but the core operational context is present.

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 description coverage is 55%, so the description needs to compensate, and it does explain several parameters: post, who_can_see, allow_* defaults, disclosure-related switches, caption, title, and owner_said. check_id is left to the schema, and the phrase 'who_can_see is the value they picked from who_can_see' is circular rather than adding clarity.

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?

The description states a specific action (the owner's answer to a waiting TikTok post) and explains the two outcomes: post true sends it, post false drops and refunds it. It references social_post_check as the preceding tool, which helps distinguish the workflow, though the opening sentence is somewhat narrative rather than a crisp verb+resource statement.

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?

It clearly establishes the trigger: after showing the owner what social_post_check returned and obtaining their reply. It also gives the key constraint, 'Never choose for them: TikTok requires that they do,' but does not explicitly state when-not-to-use conditions or other alternatives beyond social_post_check.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Conecto tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?