Skip to main content
Glama

PostWire

by io.github.Perufitlife
OverviewDiscussionsAdmin

Get a link to connect a social account

create_connect_link

Creates a one-hour link the user opens in a browser to connect a social account (TikTok, YouTube, LinkedIn, Bluesky…) to their PostWire account. Nothing is connected until the user completes it on the page. With brand_id the account is connected to that brand. Returns the url of that page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brand_idNoBrand to connect it to. Omit for the default brand.
platformNoPlatform to connect. Omit to let the user choose on the page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / brand_id
      Added value: +{
+  "description": "Brand to connect it to. Omit for the default brand.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations indicate a non-readonly, non-destructive operation. The description adds crucial behavioral details: the link expires in one hour, nothing is connected until the user completes the action, and the return value is the URL. This goes beyond the annotations.

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 three concise sentences with no filler, front-loading the primary purpose. Every sentence contributes 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 a simple tool, it covers the essential aspects: purpose, expiry, completion requirement, and return value. No output schema exists, but the description adequately sets expectations.

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 covers both parameters with descriptions, but the description adds behavioral nuance: with brand_id the account connects to that brand, and omitting platform lets the user choose on the page. This enhances the schema's information.

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 states a specific verb ('creates') and resource ('one-hour link to connect a social account'), clearly distinguishing it from sibling create tools like create_brand and create_upload_link. The purpose is unambiguous.

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 provides clear context on when to use the tool (to connect a social account) and explains the optional brand_id and platform parameters with their effects. It doesn't explicitly exclude alternatives, but the purpose is distinct enough.

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

All PostWire toolsInspect
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