Skip to main content
Glama

delimit_social_target_config

Configure social target scanning: update providers, enable/disable platforms, add subreddits, and check status for platforms like X, Reddit, GitHub, HN, Dev.to, NamePros.

Instructions

Configure social target scanning platforms (Pro).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNostatus, detect, update, add_subredditsstatus
platformNoPlatform to configure (x, reddit, github, hn, devto, namepros)
enabledNoEnable/disable the platform (used with update action)
providerNoProvider to use, e.g. twttr241, xai, proxy, gh_cli (used with update action)
subredditsNoComma-separated subreddits to add (with add_subreddits action)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

With no annotations provided, the description must fully disclose behavioral traits. It only states 'Configure social target scanning platforms (Pro),' which implies a configuration operation but does not detail effects (e.g., whether changes are permanent, authorization needs, or side effects). This is insufficient for safe invocation.

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 extremely short (one sentence) and front-loaded with 'Configure social target scanning platforms (Pro).' While not verbose, it lacks structured detail such as listing available actions or platforms, which would aid understanding without adding excessive length.

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 tool's complexity (5 parameters with 4 distinct actions, many sibling tools), the description is incomplete. It does not explain the different actions (status, detect, update, add_subreddits) or the purpose of each parameter, leaving the agent with insufficient context to use the tool correctly.

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 description coverage is 100%, so the schema already provides descriptions for all 5 parameters. The tool description adds no extra meaning beyond the schema, meeting the baseline expectation. No improvement or degradation.

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 'Configure social target scanning platforms (Pro)' clearly indicates the tool's function: it configures platforms for social target scanning. The verb 'configure' and the noun 'social target scanning platforms' provide specific purpose. However, it does not differentiate from sibling tools like 'delimit_social_target' or other social tools, missing an opportunity to clarify its distinct role.

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 given on when to use this tool versus alternatives. Sibling tools include many social-related tools (e.g., delimit_social_target, delimit_social_accounts), but the description lacks any criteria for selection or exclusion of this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/delimit-ai/delimit-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server