Skip to main content
Glama
Socifyr MCP

Socifyr MCP

by Socifyr

refresh_connection

Renew an account's access token without the owner when a connection is expiring or a post fails due to an expired or invalid token, then reconnect if renewal isn't supported.

Instructions

Renew an account's access token without the owner (use when list_connections shows "expiring" or a post failed with an expired/invalid token). Works only for accounts that can refresh; if it fails, call reconnect_connection.

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": "refresh_connection"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does well: it says the operation is performed without the owner, is limited to refreshable accounts, and that failure should route to reconnect_connection. It does not state side effects on the existing token or any permission requirements, which keeps it short of a 5.

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?

Two tight sentences, front-loaded with the action, then conditions, then the escape hatch. No filler or redundant restatement of the tool name.

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 one-parameter mutation tool with no annotations and no output schema, the description covers when to call it, its constraint, and its failure path. It stops short of saying what the caller observes on success (e.g., new expiry) or whether the old token is revoked.

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 fully (connection slug with an example), so the baseline is 3. The description adds no further detail about the slug format or whether it must match an existing connection name, leaving the schema to do all the work.

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: renew an account's access token without the owner. It immediately differentiates itself from reconnect_connection by noting the no-owner-interaction path, so an agent can choose between the two without opening 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 Guidelines5/5

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

Gives two concrete triggers (list_connections showing "expiring" or a post failing with an expired/invalid token) plus an explicit exclusion (only accounts that can refresh) and a named fallback tool (reconnect_connection) when it fails. This is the full when/when-not/alternative pattern.

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