Skip to main content
Glama

convert_grid_placeholder

Turn a placeholder into a DRAFT post at the same time slot, using the note as its caption, and remove the placeholder. The draft has no media yet and is not scheduled — it will not publish: the user adds the media and schedules it in reeldrop. Edit the caption or time with update_scheduled_post.

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": {
      "workspace_id": "<workspace_id>",
      "placeholder_id": "<placeholder_id>"
    },
    "name": "convert_grid_placeholder"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYes
placeholder_idYes

Output Schema

NameRequiredDescriptionDefault
idYes
modeYes
statusYes
captionYes
is_trialNo
ig_media_idNo
scheduled_atNo
ig_account_idYes
publish_errorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the resulting state: a draft with no media, not scheduled, that will not publish, plus the required human follow-up in reeldrop. The one gap is that it removes the source placeholder while destructiveHint=false, and it does not say whether the conversion is reversible or what happens on failure, so the annotation's safety profile is not fully reconciled.

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?

Three tight sentences, front-loaded with the action and outcome, followed by the critical 'will not publish' caveat and the routing to update_scheduled_post. Nothing is redundant with the schema or annotations.

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 an output schema (so return values need not be described), the definition covers outcome state, non-publication, and the follow-up path. The remaining shortfall is behavior around the placeholder deletion — reversibility and failure handling — which matters given destructiveHint=false.

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 0% for both parameters (workspace_id, placeholder_id), and the description never names them, though 'placeholder' and the 'same time slot'/'note' wording implicitly explain what placeholder_id identifies. workspace_id is left entirely to the schema, so the description adds only partial meaning over an undocumented schema.

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: convert a placeholder into a DRAFT post, reusing the note as caption and the existing time slot, then removing the placeholder. This is clearly distinct from siblings like create_grid_placeholder, update_grid_placeholder, and update_scheduled_post, which an agent can tell apart without opening any 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?

Explains the context of use (draft creation that intentionally does not publish; the user finishes media and scheduling in reeldrop) and names the follow-up tool for edits ('Edit the caption or time with update_scheduled_post'). It stops short of explicit exclusions, e.g. when to create a placeholder instead of converting one, but the post-conversion workflow is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources