Skip to main content
Glama
olamide-olaniyan

SociaVault MCP Server

get_instagram_profile

Retrieve Instagram profile information including bio, follower counts, and posts by providing a username. This tool extracts public data from Instagram profiles for analysis or verification purposes.

Instructions

Get Instagram profile data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
handleYesInstagram username

Implementation Reference

  • The handler logic within the CallToolRequestSchema request handler that executes the get_instagram_profile tool: makes an API call to Sociavault's Instagram profile endpoint using the provided handle, extracts data with extractInstagramProfile, and returns formatted JSON.
    if (name === "get_instagram_profile") {
      const { handle } = args as { handle: string };
      const response = await axios.get(`${BASE_URL}/instagram/profile`, {
        headers: { "X-API-Key": API_KEY },
        params: { handle },
      });
      const extracted = extractInstagramProfile(response.data);
      return {
        content: [{ type: "text", text: JSON.stringify(extracted, null, 2) }],
      };
    }
  • src/index.ts:212-222 (registration)
    Registration of the get_instagram_profile tool in the tools array used by the MCP server's ListToolsRequestSchema handler.
    {
      name: "get_instagram_profile",
      description: "Get Instagram profile data",
      inputSchema: {
        type: "object",
        properties: {
          handle: { type: "string", description: "Instagram username" },
        },
        required: ["handle"],
      },
    },
  • Input schema definition for the get_instagram_profile tool, specifying a required 'handle' string parameter.
    inputSchema: {
      type: "object",
      properties: {
        handle: { type: "string", description: "Instagram username" },
      },
      required: ["handle"],
    },
  • Helper function that parses and extracts key Instagram profile fields from the raw API response data.
    function extractInstagramProfile(data: any) {
      const user = data?.data?.user || data?.user || {};
      return {
        username: user.username,
        full_name: user.full_name,
        biography: user.biography,
        followers: user.edge_followed_by?.count || 0,
        following: user.edge_follow?.count || 0,
        posts_count: user.edge_owner_to_timeline_media?.count || 0,
        is_verified: user.is_verified,
        is_private: user.is_private,
        is_business: user.is_business_account,
        external_url: user.external_url,
        profile_pic_url: user.profile_pic_url,
      };
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Get Instagram profile data' implies a read-only operation but doesn't specify authentication requirements, rate limits, data freshness, or what happens with invalid handles. For a tool accessing external APIs with no annotation coverage, this leaves significant behavioral questions unanswered.

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?

The description is extremely concise at just four words, front-loading the essential purpose with zero wasted words. Every word earns its place, making it immediately scannable and understandable despite its brevity.

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

Completeness2/5

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

For a tool with no annotations, no output schema, and accessing external social media data, the description is insufficiently complete. It doesn't explain what profile data is returned (basic info, statistics, media), authentication needs, rate limits, or error handling. The context signals show this is a simple single-parameter tool, but the external API nature requires more disclosure than provided.

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?

The input schema has 100% description coverage with 'handle' clearly documented as 'Instagram username'. The description doesn't add any parameter semantics beyond what the schema provides (no format examples, character limits, or validation rules). With complete schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but doesn't need to.

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 'Get Instagram profile data' clearly states the verb ('Get') and resource ('Instagram profile data'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'get_instagram_posts' which also retrieves Instagram data, nor does it specify what aspects of a profile are retrieved (bio, followers, etc.).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'get_instagram_posts' and 'get_tiktok_profile' available, there's no indication whether this is for basic profile info versus posts, or how it differs from other social media profile tools. No exclusions or prerequisites are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/olamide-olaniyan/sociavault-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server