Enterprise Threads MCP Server

website_integration_setup

Set up Threads integration for websites and platforms, including feed embedding, share buttons, auto cross-posting, and webhook setup.

Instructions

Setup Threads integration for websites and external platforms

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": {
      "integration_type": "<integration_type>"
    },
    "name": "website_integration_setup"
  }
}

Input Schema

Name	Required	Description
`website_config`	No
`integration_type`	Yes	Type of integration to setup
`automation_settings`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv5.1.0Aug 14, 2026

TDQS

C2.6/5.0

Behavior2/5

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

With no annotations, the description carries the full burden for behavioral disclosure. It only says 'Setup' without indicating whether this is a write operation, whether it modifies external systems, requires authentication, or what side effects occur. This is a significant gap for a setup tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief and front-loaded, but it is under-specified for the tool's complexity. It does not waste words, yet the single vague sentence lacks substance while not being overly verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complex nested schema, multiple integration types, and no output schema or annotations, the description is far from complete. It provides no context on what the setup entails, return values, or expected behavior, making it inadequate for safe invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 33% description coverage, and the tool description adds no parameter information at all. It doesn't explain the meaning of integration_type or the nested objects, so the agent must rely solely on the incomplete schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool sets up Threads integration for websites/external platforms, using the verb 'Setup' with a specific resource. It distinguishes from sibling publishing/analysis tools, though 'Setup' is a bit generic and could be more explicit about creating a configuration.

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?

No guidance is provided on when to use this tool versus alternatives, prerequisites, or what scenarios it fits. It does not mention related tools like validate_setup, leaving the agent to infer usage from the name and schema.

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

Deploy Server