Skip to main content
Glama
unofficial-instagram-mcp

unofficial-instagram-mcp

feed_home

Read-only

Retrieve the logged-in account's home timeline, including recent posts and their authors, with an optional limit to control how many entries are returned.

Instructions

Intip timeline beranda akun yang login (postingan terbaru + penulisnya).

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that results include post authors, which is a small amount of context about the shape of the result, but it says nothing about ordering guarantees, pagination, or freshness beyond "terbaru".

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?

One tight sentence with no filler, and the core scope (logged-in home timeline) is front-loaded. It is arguably a bit too terse given the undocumented parameter, but nothing is wasted.

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 single-parameter read tool with annotations and no output schema, the description covers purpose and payload adequately. The remaining gap is the undocumented `limit` parameter, which a caller needs in order to page or cap results correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single optional parameter `limit` has 0% schema description coverage, and the description never explains it. "Postingan terbaru" hints that results are recency-ordered, but the agent gets no guidance on what limit controls, its units, defaults, or bounds.

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 names a specific verb and resource ("Intip timeline beranda" – peek at the home timeline) and specifies the payload ("postingan terbaru + penulisnya" – latest posts plus their authors). It clearly scopes to the logged-in account's feed, which distinguishes it from siblings like user_posts or explore_posts, though it never names those alternatives explicitly.

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?

The phrase "akun yang login" implies this is the tool for the authenticated user's own feed, so the usage context is inferable but never stated. There is no explicit when-to-use versus explore_posts/hashtag_posts/user_posts, and no exclusions or prerequisites.

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