Skip to main content
Glama

get_grid

Read-onlyIdempotent

The Instagram profile as a grid board: the latest published tiles, the posts planned to go out (drafts and scheduled), and the placeholders ("idea" tiles with a note and a time slot) — the layout the user would see in reeldrop's grid planner.

published_limit is 3–30. Reading the grid first picks up posts published straight from the Instagram app, so it can make a few Instagram calls on a large account. Use it to answer "what will my grid look like next week?" or to find the ids that update_grid_placeholder, convert_grid_placeholder and swap_grid_entries take. Instagram's pinned posts are not reported by its API, so a pinned post appears in date order here.

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

Input Schema

NameRequiredDescriptionDefault
workspace_idYes
published_limitNo

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 already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered; the description still adds real value by disclosing that reading the grid first can trigger several Instagram API calls on a large account, and that pinned posts are not reported by Instagram's API and therefore appear in date order. These are non-obvious cost and data-fidelity caveats not derivable from the annotations or schema.

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?

The description is front-loaded: the first paragraph defines the returned structure, the second gives the constraint, side-effect warning, usage routing, and the pinned-post caveat. The em-dash-heavy first sentence is dense but each paragraph contributes information; minor tightening would be possible but nothing is filler.

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?

With an output schema present, the description needn't enumerate return fields, and it instead gives the right conceptual shape plus caveats an agent needs before calling. The main gap is that workspace_id semantics (scope of the grid) and any pagination behavior are not addressed, though the tool is otherwise fully specified for correct invocation.

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%, so the description must carry parameter meaning. It does explain published_limit well — the 3–30 range and, implicitly, that it controls how many published tiles are fetched (with the schema default of 12) — but workspace_id is never mentioned, leaving one of the two parameters entirely to the schema's bare type declaration.

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?

The description states a concrete verb and resource — it returns an Instagram profile as a grid board containing published tiles, planned posts (drafts and scheduled), and idea placeholders — and names the exact layout the user sees in the grid planner. This is clearly distinguishable from sibling tools like update_grid_placeholder or swap_grid_entries, which mutate single entries rather than read the whole board.

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?

It gives two explicit usage scenarios ('what will my grid look like next week?' and 'find the ids that update_grid_placeholder, convert_grid_placeholder and swap_grid_entries take'), which effectively routes the agent to this tool as a prerequisite for the mutation siblings. It stops short of saying when not to use it or naming a direct alternative reader, so a 4 rather than a 5.

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