Xyla AI

Connect a social account

connect_account

Makes a one-use link that connects a social account to this Xyla shop, or reconnects a broken one. Give the merchant the link to open in their browser; it works once and expires in 10 minutes, and asks for the store's email. To reconnect an account from connection_status, pass its social_media_account_id. Instagram has two ways in: instagram_direct (Instagram Login, the usual choice) and instagram (through a Facebook Page, needed for Stories and product tags). Disconnecting stays on the Xyla website.

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": {
      "provider": "<provider>"
    },
    "name": "connect_account"
  }
}

Input Schema

Name	Required	Description	Default
`provider`	Yes	The platform to connect.
`social_media_account_id`	No	The account to reconnect, from connection_status. Leave out to connect a new account.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only declare the safety profile (readOnlyHint=false, openWorldHint=true, non-idempotent, non-destructive). The description goes well beyond that with operational traits an agent needs: the link is one-use, expires in 10 minutes, the merchant must open it in a browser, and it prompts for the store's email.

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?

Four tight sentences with no filler; the core action and its one-use/expiry constraints are front-loaded, and the provider nuance and disconnect exclusion follow in priority order. Every clause carries information an agent would otherwise have to guess.

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 no output schema, the description carries the return-value burden: it implies a link is produced but never names the response field or whether the link is returned in the tool result versus emailed. Otherwise complete — provider routing, expiry, reconnection path and prerequisites are all covered.

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 coverage is 100%, so the baseline is 3, but the description adds meaning the schema lacks: it explains that social_media_account_id should be sourced from connection_status and that omitting it means a new connection. The Instagram provider trade-off is likewise explained in prose rather than left to the enum.

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 — 'makes a one-use link that connects a social account to this Xyla shop' — and explicitly scopes the reconnection case. It also carves out what this tool does NOT do ('Disconnecting stays on the Xyla website'), so an agent can separate it from connection_status and the settings siblings.

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 concrete when-to-use guidance: reconnect by passing social_media_account_id from connection_status, omit it for a new connection. It also resolves the ambiguous Instagram choice by naming instagram_direct as 'the usual choice' and explaining when the Facebook-Page route is required (Stories, product tags).

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

All Xyla AI 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?