Skip to main content
Glama

swap_grid_entries

Swap the time slots of two planned tiles — the grid's drag-to-reorder. Each ends up with the other's time. A kind is "post" (a draft or scheduled post, by its post id) or "placeholder". A published post cannot be moved.

Swapping a scheduled post moves when it will actually be published, so check the two times with the user first. If the second move fails the first is put back and nothing changes. Returns the updated grid.

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>",
      "first_kind": "<first_kind>",
      "first_id": "<first_id>",
      "second_kind": "<second_kind>",
      "second_id": "<second_id>"
    },
    "name": "swap_grid_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
first_idYes
second_idYes
first_kindYes
second_kindYes
workspace_idYes

Output Schema

NameRequiredDescriptionDefault
noteYes
plannedYes
has_moreYes
usernameNo
publishedYes
media_countNo
placeholdersYes
follows_countNo
showing_last_nYes
followers_countNo
total_publishedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare the generic profile (not read-only, not destructive, not idempotent, open-world); the description adds genuinely non-redundant behavior: side effect on actual publish time, atomic rollback semantics ('if the second move fails the first is put back and nothing changes'), and the published-post constraint. It does not cover permissions/authorization needed for the mutation, which is the remaining gap.

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 core action and outcome, then the safety-relevant caveats. Sentences are short and purposeful, with only mild redundancy between 'swap the time slots' and 'each ends up with the other's time'.

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 5-required-parameter mutation with annotations present and an output schema available, the definition covers outcome, constraint, failure mode, and user-confirmation duty. Missing workspace scoping and permission expectations keep it from being fully complete.

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?

With 0% schema description coverage the description must carry the parameters, and it does explain the kind/id pairing ('a kind is "post" ... by its post id, or "placeholder"') — valuable since no enum exists in the schema. However workspace_id is never mentioned and the id semantics for the placeholder kind are left implicit, so coverage is partial rather than compensating fully.

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?

Names a specific verb and resource ('swap the time slots of two planned tiles') and immediately anchors it to a familiar interaction ('the grid's drag-to-reorder'), then states the outcome ('each ends up with the other's time'). An agent can distinguish this from update_grid_placeholder or convert_grid_placeholder 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?

Gives a clear precondition (both entries must be planned tiles) and an explicit prohibition ('a published post cannot be moved'), plus a confirmation gate for scheduled posts. It stops short of naming a sibling alternative for the cases it rules out, so it is strong context rather than a full when/when-not routing rule.

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