Skip to main content
Glama

Link for someone to connect their account

create_connect_link

Make a link that lets someone else (a client, a teammate) connect their own social account to THIS Octopost account with no Octopost login. Give them the url; each account they connect shows up in list_accounts. Works 7 days by default, for up to 5 accounts. The url is shown once.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_connect_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNoWho it is for, shown on the link page.
networksNoOnly these networks. Omit for any.
max_accountsNo1 to 25 (default 5).
expires_in_daysNo1 to 30 (default 7).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (which only say this is not read-only, not destructive, not idempotent), the description discloses the two facts that most affect correct invocation: the link expires in 7 days by default and the url is shown only once, so it must be captured immediately. It also explains the recipient needs no Octopost login and that connected accounts appear in list_accounts.

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?

Four short sentences, front-loaded with the purpose and the action to take with the url. The one weakness is that the default lifetime and account cap restate what the schema already declares, which is mild redundancy rather than bloat.

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?

With four optional parameters, full schema coverage, and no output schema, the description covers the essentials an agent needs: what the link is for, its lifetime, its account cap, and the one-time display of the url. It does not address whether a link can be revoked or regenerated, a small remaining gap.

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

Parameters3/5

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

Schema description coverage is 100%, so label, networks, max_accounts, and expires_in_days are already documented with their ranges and defaults. The description repeats the 7-day and 5-account defaults but adds no new meaning beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb and resource (make a link) plus the exact scope: someone else connects their own social account to THIS Octopost account without an Octopost login. It also distinguishes the outcome from the sibling tool list_accounts, which is where connected accounts surface, so an agent can place it in the workflow.

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?

The use case is explicit: hand the url to a client or teammate so they can connect accounts on their own. It names the follow-up tool (list_accounts) where results appear. It stops short of stating when NOT to use it or what alternative exists for adding accounts directly, but the positive guidance is unambiguous.

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