Skip to main content
Glama
Sign In

Systra Tools

by tools.systra
OverviewDiscussionsAdmin

List post templates

list_posts
Read-onlyIdempotent

Lists the Instagram post templates (1080 x 1350) with slug, name, family and whether they need your own imagery. Each template is a single HTML file that can be rebuilt and exported as an image or a video. Pass query to search by name or purpose, for example 'quote' or 'statistic'. Use it to pick a slug for get_post.

Input Schema

NameRequiredDescriptionDefault
queryNoSearch term (optional). Every word must appear in the slug, name, purpose or family. Can be combined with family.
familyNoFamily to filter by (optional): 'klar' are calm informational posts, 'editorial' lives on the image and a serif face.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / query
      Added value: +{
+  "description": "Search term (optional). Every word must appear in the slug, name, purpose or family. Can be combined with family.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / family / description
      Previous value: -"Familie zum Filtern (optional): 'klar' sind ruhige Informationsposts, 'editorial' lebt von Motiv und Serifenschrift."New value: +"Family to filter by (optional): 'klar' are calm informational posts, 'editorial' lives on the image and a serif face."
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-open-world, and the description adds real context beyond them: templates are single HTML files that can be rebuilt and exported as image or video, and it names the fields each entry carries. It omits nothing critical for a non-destructive read; minor gap is no note on result size or ordering.

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?

Four short sentences, front-loaded with what is returned, then the filter, then the downstream step. Nothing repeats structured fields and no sentence is filler.

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

Completeness5/5

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

A parameterless-filter list tool with full schema coverage and rich annotations needs nothing more; the description covers return shape, filter behavior and the follow-up call. No output schema is required because the returned fields are stated inline.

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% (baseline 3), and the description adds value on top by giving concrete query examples and stating the searchable dimensions. It slightly understates the schema's matching rule (slug, name, purpose or family) and never mentions the family enum, so it isn't a full 5.

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 (lists) and resource (Instagram post templates, 1080x1350) and enumerates the returned fields (slug, name, family, needs-imagery), which distinguishes it from get_post and the other list_* siblings by resource.

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 places the tool in a workflow: 'Use it to pick a slug for get_post,' and shows how to filter with query examples ('quote', 'statistic'). It does not compare against the other list_/search_ siblings, but the resource boundary is clear enough that an agent won't confuse them.

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

All Systra Tools toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources