Skip to main content
Glama
Sign In
Glim

Glim

by jagdish3135
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Instagram profile

ig_get_profile
Read-onlyIdempotent

Retrieve the connected Instagram professional account's profile details—username, name, bio, website, follower/following/post counts—and demo or live status to verify the connection first.

Instructions

Get the connected Instagram professional account: username, name, bio, website, followers, following and post count. Also says whether Glim is in demo mode (fictional sample account) or live. Call this first to check the connection.

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": "ig_get_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
response_formatNo'markdown' for readable text (default), 'json' for structured datamarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely non-structured context: that the response discloses demo mode (fictional sample account) vs live, which affects how the agent should interpret every subsequent call. It doesn't cover failure modes for an unconnected account.

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?

Two short sentences, zero filler, with the resource and returned fields front-loaded and the operational instruction ('call this first') placed last where it reads as a directive. Every clause carries information.

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?

With no output schema, the description compensates by listing the exact fields returned, and it also explains the demo/live distinction an agent needs to interpret results. Nothing required to call it correctly is missing.

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?

There is one optional parameter, response_format, documented at 100% schema coverage with its enum and default. The description says nothing about output format selection, so the schema is doing all the work; baseline 3 applies.

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 (Get) and resource (connected Instagram professional account) and enumerates exactly what comes back: username, name, bio, website, followers, following, post count. No sibling tool in the list retrieves profile data, so the resource alone disambiguates it.

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?

'Call this first to check the connection' gives explicit ordering guidance an agent can act on, which is unusually concrete for a read tool. It does not name any alternative or when-not condition, but for a single-purpose profile fetch there is no plausible competing 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