Skip to main content
Glama
Sign In

Dropspace

by io.github.JCLVSH
OverviewDiscussionsAdmin

update_connection_profile

Destructive

edit the connected account's profile ON the platform. youtube only today: sets the channel description (max 1,000 characters; an empty string clears it) via channels.update. instagram's api can read a profile but not write it, facebook page "about" needs a permission dropspace does not hold, and tiktok / x / linkedin expose no profile write - those return an error with the reason. requires the write scope.

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>",
      "description": "<description>"
    },
    "name": "update_connection_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformYesplatform whose profile to edit (currently only "youtube")
descriptionYesthe new profile / channel description (max 1,000 characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag a non-read-only, destructive operation; the description adds real context on top – the required write scope, that an empty string clears the description, and the failure mode for unsupported platforms. It does not describe the response payload, but no output schema exists and the mutation semantics are otherwise well disclosed.

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 action and the platform constraint, then the per-platform reasons, then the permission requirement. Dense but every clause carries information; the platform-caveat list is slightly sprawling but not wasteful.

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 two-parameter mutation with no output schema, the description covers scope, permission, clearing semantics, and error behavior for unsupported platforms. Only the success response shape is unstated, which is a small omission given the tool's simplicity.

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 baseline is 3, but the description adds meaning the schema lacks: the empty-string-clears behavior for `description` and the fact that `platform` is effectively constrained to youtube despite being a free-form string. That is genuine value beyond the structured fields.

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 ('edit the connected account's profile') and immediately narrows scope to the one platform it actually supports ('youtube only today'), with the underlying API call (channels.update) named. An agent can tell exactly what this does 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 Guidelines4/5

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

Explicitly says which platforms are unsupported and why (instagram read-only, facebook needs a missing permission, tiktok/x/linkedin have no write), and that those attempts return an error with the reason. It also states the write-scope prerequisite. No sibling alternative is named, but none of the listed siblings appear to do profile writes, so the gap is minor.

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

All Dropspace 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