Skip to main content
Glama
Sign In

WoopSocial Social Media MCP

by com.woopsocial
OverviewDiscussionsAdmin

Delete social account

social_accounts_delete
DestructiveIdempotent

Deletes one social account connection by ID.

This removes the associated OAuth grant, including stored access and refresh tokens, so the account no longer counts toward the organization's active connected-account allowance.

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": {
      "socialAccountId": "<socialAccountId>"
    },
    "name": "social_accounts_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
socialAccountIdYesConnected social account identifier.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

The description adds substantial behavioral detail beyond the annotations by specifying exactly what is removed: the associated OAuth grant, stored access and refresh tokens, and the effect on the organization's active connected-account allowance. With annotations already declaring destructive=true and idempotent=true, this extra context is valuable and accurate.

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 tightly written sentences front-load the core action and then explain the key consequence. Every sentence earns its place, with no redundant or filler content.

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 simple, one-parameter destructive operation with rich annotations and no output schema, the description is largely complete: it identifies what is deleted, what credentials are removed, and a billing-related side effect. It could optionally mention irreversibility or side effects on associated posts, but the annotations already flag the destructive nature.

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%, with the single parameter 'socialAccountId' fully described in the schema. The description only repeats 'by ID' and does not add format, source, or lookup guidance beyond what the schema provides, so the baseline of 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 states a specific verb ('Deletes') and resource ('one social account connection') with clear scope ('by ID'), which distinguishes it from sibling tools like social_account_posts_delete and social_accounts_list. An agent can identify the correct operation without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description explains the consequence of deletion but provides no explicit guidance on when to use this tool versus alternatives such as social_account_posts_delete or social_accounts_list. Usage is only implied by the name and verb, so an agent must infer the correct context.

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

All WoopSocial Social Media MCP toolsInspect
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