instagram-nutrition-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IG_USER_ID | No | Instagram user ID. Required for publishing (noted as a future feature). | |
| IG_TOKEN_JSON | No | Path to the stored token file. | .tokens/token.json |
| IG_API_VERSION | No | Instagram API version to use. | v24.0 |
| IG_ACCESS_TOKEN | Yes | Instagram/Meta access token. Both Instagram-login (IGAA...) and Facebook-login (EAB...) tokens work. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_tokenA | Check that the Instagram access token works, which account it belongs to, and when it expires (if known). Use this when Instagram calls fail or to see if a refresh is due. |
| get_account_infoA | Get the connected Instagram account's username, name, account type, follower and following counts, and number of posts. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
check_token is a diagnostic/auth-health tool while get_account_info returns profile metadata, so their primary purposes are distinct. There is mild overlap since check_token also reveals which account the token belongs to, but description context makes the boundary clear enough.
Both tools follow a uniform snake_case verb_noun pattern (check_token, get_account_info). The convention is predictable and easy to extend.
Only two tools exist, both of which are preliminary/setup-oriented (token check and account lookup). For a server branded around Instagram nutrition data, this surface is far too thin to earn its place.
There are no tools to fetch posts, media, captions, or any nutrition-related content, which is the apparent purpose of the server. The surface covers only connectivity and account identity, leaving core workflows as dead ends.