FeedSquad

Connect Platform

connect_platform

Connects a social media platform (LinkedIn, X/Twitter, or Threads) to the FeedSquad account. For X and Threads, returns a single-use FeedSquad start URL valid for 10 minutes; it works in a browser signed in to the same FeedSquad account, before the platform is authorized. LinkedIn returns its authorization URL. When the platform is already connected it returns already_connected: true with the connected account labels (connected_accounts) and connections_url instead of a URL. A second X account, such as a brand account, is added from connections_url, not through this tool.

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": {
      "platform": "<platform>"
    },
    "name": "connect_platform"
  }
}

Input Schema

Name	Required	Description	Default
`platform`	Yes	The platform to connect: linkedin, twitter, or threads

Output Schema

Name	Required	Description	Default
`kind`	Yes
`message`	Yes
`platform`	Yes
`oauth_url`	No
`expires_in`	No
`platform_label`	No
`connections_url`	No
`already_connected`	Yes
`connected_accounts`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations: single-use URL with a 10-minute validity window, the requirement that the browser be signed in to the same FeedSquad account, platform-specific return differences (LinkedIn auth URL vs. X/Threads start URL), and the already_connected response shape. Nothing here contradicts the declared non-read-only, non-idempotent, open-world profile.

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?

Front-loaded with the core action, then conditional behavior in the order an agent would need it. The sentences are long but each carries distinct information; a small amount of density could be trimmed without loss.

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?

Covers the branching outcomes (URL returned, already_connected with connected_accounts and connections_url) and the cross-account constraint, which is the risky edge case for this tool. With an output schema present, return-value details need not be spelled out further.

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 coverage is 100% and there is only one parameter, so the schema already carries the semantics. The description names the platforms again but adds no syntax beyond the enum, and its phrasing ('LinkedIn, X/Twitter, or Threads') does not perfectly mirror the four enum values (linkedin, x, twitter, threads).

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 ('Connects a social media platform ... to the FeedSquad account') and names the supported platforms explicitly. It is clearly distinct from siblings like list_accounts or publish_post, and even carves out the second-X-account case as out of scope.

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 explicit when-not guidance ('A second X account ... is added from connections_url, not through this tool') and effectively tells the agent what to expect if the platform is already connected. The alternative path (connections_url) is named directly, so the agent can route correctly without guessing.

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

All FeedSquad tools Inspect

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

Need Help?