Skip to main content
Glama

인스타그램 프로필 조회

instagram_profile
Read-only

Instagram public profile: followers, following, posts count, bio, verification and the 12 latest posts. 인스타그램 공개 계정의 팔로워·팔로잉·게시물 수·소개·인증 여부와 최근 게시물 12개를 조회합니다. 처리에 보통 5~10초가 걸립니다. [호출당 20포인트]

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

Input Schema

NameRequiredDescriptionDefault
urlNo인스타그램 프로필 주소 (예: https://www.instagram.com/natgeo/)
usernameNo인스타그램 사용자명 (username 또는 url 중 하나 필수)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds useful operational context beyond annotations: typical processing time of 5–10 seconds and a cost of 20 points per call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is front-loaded and informative, but the full English and Korean duplication roughly doubles the length for the same information. The latency and cost notes are valuable and not repeated elsewhere.

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 no output schema, the description appropriately names the return fields and the 12-post limit. It also covers latency and cost. Minor gap: it does not clarify whether private accounts fail or how errors are surfaced.

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%, so both 'url' and 'username' are fully documented in the schema, including the requirement that one is needed. The description itself adds no further parameter guidance, which is acceptable at full schema coverage.

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 and resource ('Instagram public profile') and enumerates exactly what is returned: followers, following, posts count, bio, verification, and the 12 latest posts. This is clearly distinct from instagram_post and other siblings.

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 implied by 'public profile' and the returned data, but the description does not explicitly say when to use this versus instagram_post or other profile tools. No exclusions or alternatives are named.

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.