uplika

Select channels to post to

select_channels

Read-only

Pick which connected channels to post to. Call this before publish and show the result to the person. Leave scope empty to get the candidate list and let them choose. Use scope: "all" for every active channel, or an array mixing platform names ("threads"), handles ("@vibe.trender") and account ids. Duplicates are folded, expired and not-yet-live channels are dropped into skipped with a reason, a sentence you can read to the person, and a link to reconnect. Pass the returned accountIds to publish unchanged. limits is the tightest rule across the chosen channels, so write to that. If both accountIds and candidates come back empty, nothing is connected yet. Send the person to https://uplika.com/dashboard/connections to connect a channel, then call this again.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`scope`	No	Omit to list candidates, "all" for every active channel, or an array of platform names, handles or account ids.
`workspaceId`	No	Which workspace this is for. Only needed when the account has more than one — the error tells you the ids when it matters. Leave it out if it is already decided; do not ask the person again.

TDQS

A5/5.0

Behavior5/5

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

The description adds substantial behavior beyond the readOnlyHint annotation: duplicate folding, dropping expired/not-yet-live channels into `skipped` with a reason and link, the meaning of `limits`, and the instruction to pass `accountIds` to publish unchanged. It also clarifies the empty-candidates edge case. This fully discloses the tool's runtime behavior.

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 dense but every sentence carries essential guidance. It is front-loaded with the most important instruction ('Call this before publish') and then logically proceeds through scope options, result handling, and fallback. No word is wasted; the length is justified by the tool's complexity.

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

Completeness5/5

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

With no output schema, the description fully explains what the tool returns: candidates, skipped list, limits, accountIds, and the empty case. It also provides connection-recovery guidance. This is complete for a selection tool in this context, covering all observable outcomes and the publish linkage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

While the schema already describes both parameters (100% coverage), the description greatly enriches their semantics: scope's omit-vs-all-vs-array behavior, workspaceId's optionality and error-driven prompting, and the relationship of the returned `accountIds` to publish. This goes well beyond the schema's basic 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 opens with 'Pick which connected channels to post to,' which is a specific verb and resource. It clearly distinguishes from sibling tools like publish, list_channels, and get_quota by framing this as the channel-selection step before publishing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs 'Call this before publish and show the result to the person.' It also explains when to omit scope (candidate list), when to use "all", and how to handle mixed arrays. The fallback guidance for empty results (send to connection dashboard) provides clear when-to-use context and a next step.

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

All uplika tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation4/5

Most tools have clearly distinct purposes, and descriptions actively steer usage (e.g., get_post vs open_post, list_posts vs list_channel_posts). A few pairs like list_accounts vs select_channels or get_post vs open_post still require careful reading to pick the right one, but the overlap is manageable.

Naming Consistency4/5

The dominant pattern is verb_noun (delete_post, get_insights, list_accounts, select_channels), which is consistent and predictable. A few bare-verb names like publish and reply, plus the media_* prefixed tools, break the strict pattern but still feel coherent within their subdomains.

Tool Count4/5

20 tools is on the heavier side, but the breadth is justified by the server's scope: publishing, media upload workflows, reply threads, insights, quotas, and account selection. Each tool has a real job, though the four post-retrieval variants and five media tools could feel redundant at a glance.

Completeness4/5

The core lifecycle is well covered: publish, reply, delete, retry, retrieve, list, and get insights, plus multi-step media handling. Minor gaps exist, such as no general post editing, no delete-reply action beyond hiding, and limited scheduling outside YouTube, but these are not critical for the stated purpose.

Resources

Need Help?