Skip to main content
Glama
Sign In
slidecold-mcp

slidecold-mcp

by slidecold
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List Instagram accounts

list_accounts
Read-onlyIdempotent

Lists Instagram accounts available to the connected SlideCold workspace, optionally filtered by folder, so agents can select accounts for outreach or review.

Instructions

List Instagram accounts. Required API key scope: accounts:read. GET /accounts

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
folderIdNoFolder id, or `root` for items not in any folder.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered. The description adds genuinely new behavioral context by disclosing the required API key scope (accounts:read) and the underlying endpoint (GET /accounts), which an agent cannot infer from the annotations; however, it says nothing about pagination or result limits for a list operation.

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?

Three short lines with the purpose front-loaded, followed by the auth scope and endpoint - no filler or repetition. It is tightly written, though the endpoint line contributes little for an agent that already has the tool abstraction.

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 simple list tool with one optional parameter and no output schema, the essentials are present, but the description omits whether results are paginated, whether all accounts are returned, and what identifying fields each account carries. These gaps matter for a list endpoint an agent must reason about.

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% and the single folderId parameter is fully documented in the schema, including the `root` sentinel, so the baseline is 3. The description adds no meaning beyond that and never mentions folderId, so it does not exceed the baseline.

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 states a specific verb and resource ("List Instagram accounts"), which is unambiguous and clearly distinguishes it from get_account, create_account, or list_campaigns. It stops short of explicitly naming how it relates to those siblings (e.g., that get_account is for a single account's details), so it is clear but not fully differentiated.

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?

Usage is only implied by the verb "List"; there is no statement of when to call this versus get_account or get_accounts_proxy_health. The one concrete piece of guidance is the permission prerequisite ("Required API key scope: accounts:read"), which tells the agent what auth is needed but not when to choose the tool.

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

Deploy Server

Other Tools