Skip to main content
Glama
Socifyr MCP

Socifyr MCP

by Socifyr

reconnect_connection

Generates a short-lived, single-use link to re-authorize an expired account token, letting the user restore the connection in place so scheduled posts resume working.

Instructions

Get a short-lived, single-use link to re-authorize an account whose token expired or cannot refresh (status "needs_reconnect", or a post failed with "reconnect_required"). Give the link to the user to open in a browser; the account and its slug are updated in place, so scheduled posts keep working. After they approve, retry the post. Owner-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": {
      "connection": "<connection>"
    },
    "name": "reconnect_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
connectionYesConnection slug, e.g. "x-mybrand"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.5/5.0
Behavior5/5

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

No annotations exist, so the description carries the full behavioral burden, and it does: the link is short-lived and single-use, the account and slug are updated in place, existing scheduled posts keep working, the operation is owner-only, and a post retry is needed afterward. These are exactly the mutation and workflow traits an agent cannot infer from the schema.

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 definition is front-loaded with the action, then the trigger, then the follow-up workflow, then the permission constraint. Every clause carries new information, and none of it repeats the schema or title.

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?

For a one-parameter tool with no output schema, the definition covers the return value (a short-lived single-use link), the precondition, the in-place side effects, and the post-approval step. An agent has everything it needs to call it and to tell the user what to do next.

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?

There is a single required parameter and the schema already documents it at 100% coverage with an example slug. The description only echoes the notion of a slug ('the account and its slug are updated in place') and adds no format or validation detail beyond the schema, so the baseline 3 applies.

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 gives a specific verb plus resource: 'Get a short-lived, single-use link to re-authorize an account.' It also scopes the tool to accounts that cannot refresh, which distinguishes it from refresh_connection without the agent needing to open either schema.

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 names precise triggers: status "needs_reconnect" or a post that failed with "reconnect_required". It also says what to do next (give the link to the user, then retry the post) and notes the owner-only restriction. It never names refresh_connection as the path for accounts that can still refresh, so that routing decision is left implicit.

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