Skip to main content
Glama
Sign In

Dropspace

by io.github.JCLVSH
OverviewDiscussionsAdmin

update_launch

Destructive

update a launch (cannot update running/completed/partial launches)

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": {
      "id": "<id>"
    },
    "name": "update_launch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYeslaunch ID
nameNolaunch name/title
mediaNoinline media (URL or base64, 1-10 items, mutually exclusive with media_assets)
statusNolaunch status. "paused" holds a scheduled launch: it keeps its scheduled_date and does not publish until "scheduled" is sent to resume it (send a new scheduled_date too if the time has passed). "cancelled" clears the date
platformsNotarget platforms for this launch
media_modeNomedia mode
persona_idNopersona ID for content generation, null to clear
product_urlNoproduct URL (empty string to clear)
media_assetsNopre-uploaded media asset references (mutually exclusive with media)
scheduled_dateNoISO 8601 datetime or null to clear
attribution_modeNohow official-account posts credit the author ("handle" default, "anonymous" for the plain note)
platform_contentsNoper-platform content update (deep-merged with existing). each value can include "content" (string). Instagram takes "instagram_settings": { "post_type": "feed" | "carousel" | "story" | "trial_reel", "graduation_strategy"?: "MANUAL" | "SS_PERFORMANCE" } ("carousel" posts every attached image and the launch video as ONE carousel, 2 to 10 items; "trial_reel" posts the video as a reel shown to non-followers first, graduating per graduation_strategy; needs a professional account with 200 or more followers, or the update is refused with the reason) and Facebook takes "facebook_settings": { "post_type": "feed" | "story" }. Twitter supports "thread" (string[]) instead. Reddit "title" is optional on update, and "metadata" accepts "subreddits" (string[], max 10, no r/ prefix — one post per subreddit) and "first_comment" (string, max 1500). TikTok "tiktok_settings" is deep-merged — you can update individual fields (e.g. just "privacy_level") without overwriting the rest. see create_launch for full field details
dropspace_platformsNoofficial dropspace account platforms
product_descriptionNoproduct description
media_attach_platformsNoplatforms to attach media to
user_platform_accountsNomap of platform key to token_id (UUID). a simple key targets your primary/only account: "twitter", "reddit", "instagram", "tiktok", "youtube". to target a SPECIFIC account when you have more than one on the same platform, use a composite key: Instagram/TikTok/YouTube/Twitter/Reddit use "instagram:<account_id>" / "tiktok:<account_id>" / "youtube:<account_id>" / "twitter:<account_id>" / "reddit:<account_id>" where <account_id> is the account entity_id from list_connections; LinkedIn uses "linkedin:personal" or "linkedin:organization:<org_id>"; Facebook posts go to a Page: a bare "facebook" key works when you have exactly one Page, using any connection id from list_connections as the value (the Page row id or the person row id) so dropspace resolves the Page; to target a specific Page among several, use a composite key, "facebook:page:<page_id>" or "facebook:<page_id>", where <page_id> is that Page row entity_id from list_connections; with several Pages and no page_id the API returns a 400 listing them. multiple keys allowed (e.g. post to two Instagram accounts at once). for Reddit, each targeted account runs its own subreddit fan-out

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so safety framing is partly covered. The description usefully adds the state restriction that gates the operation, but it says nothing about the partial-update/deep-merge behavior implied by the schema (platform_contents deep-merge, null/empty-string clearing, mutual exclusivity of media and media_assets), nor about failure modes.

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?

Two clauses, zero filler, with the resource stated first and the constraint immediately after. It is efficient, though the parenthetical packs three state names without explanation of what each state means for an update attempt.

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

Completeness3/5

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

For a destructive, 16-parameter mutation with nested objects and no output schema, the description is thin: it omits that updates are partial merges, how fields are cleared, and what happens to omitted values. The rich schema compensates for field-level detail, but the mutation semantics remain undocumented at the description level.

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 all 16 parameters, including the nested platform_contents and user_platform_accounts objects, are already documented in the schema. The description adds no parameter-level meaning, so the baseline 3 applies.

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 gives a specific verb and resource ("update a launch"), which cleanly separates it from create_launch, delete_launch, publish_launch and get_launch among the siblings. It does not explicitly name or route against those alternatives, so it stops short of full sibling differentiation.

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

Usage Guidelines3/5

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

It supplies a genuine exclusion: launches in running, completed, or partial states cannot be updated. That is useful when-not guidance, but there is no alternative named for those cases (e.g., cancel, retry, or publish instead), and no prerequisite or ordering guidance for the editable states.

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