Skip to main content
Glama
AdaptlyPost

AdaptlyPost

Official

Search Instagram Audio

search_instagram_audio
Read-onlyIdempotent

Search Instagram music and original sounds for Reels, including trending audio, and retrieve audio IDs to attach when creating or scheduling posts.

Instructions

Search Instagram music and original sounds to add to a Reel. Returns { audio } with audioId, audioType, title, displayArtist (music), igUsername (original sounds), durationMs, coverArtworkUrl, profilePictureUrl, previewUrl (a temporary audio file, expires after about 1.5 days), instagramUrl and isAdsEligible. Leave out searchQuery to get what is trending. Only audio Meta has cleared for third-party publishing comes back, which can differ from what the Instagram app shows. Only works for Instagram accounts with supportsInstagramAudio: true in list_accounts; otherwise, or when Instagram rejects the search, it fails with 400. Pass the chosen audioId, with its title and artist, in instagramConfigs[].audio of create_post, update_post or bulk_schedule_posts. Nothing is posted.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "accountId": "<accountId>",
      "audioType": "<audioType>"
    },
    "name": "search_instagram_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountIdYesThe Instagram account id from list_accounts
audioTypeYesmusic for licensed tracks, original_sound for sounds from other Instagram posts
searchQueryNoKeywords to search for. Leave out for trending audio
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to act in the workspace list_workspaces marks current. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another

Output Schema

NameRequiredDescriptionDefault
resultYesAn object with audio: one { audioId, audioType, title, displayArtist, igUsername, durationMs, coverArtworkUrl, profilePictureUrl, previewUrl, instagramUrl, isAdsEligible } per match. Pass audioId as instagramConfigs[].audio.audioId.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.22.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the bar is lower. The description still adds real behavioral context beyond them: only Meta-cleared audio is returned, results may differ from the Instagram app, previewUrl expires after ~1.5 days, and failures surface as 400. However it does not describe pagination or result-count limits for an open-world search, so it is good but not exhaustive.

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?

Front-loaded with the action and return shape, then prerequisites and downstream usage; nearly every sentence carries information. It is dense and slightly overlong, listing every return field even though an output schema exists.

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?

For a read-only search with an output schema, the description covers the capability gate (supportsInstagramAudio), failure mode (400), result staleness/expiry, and the handoff to the post-creation tools. Nothing an agent needs 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?

Schema description coverage is 100% and both audioType enum values and the trending-when-omitted behavior are already documented in the schema. The description mostly restates the trending rule and adds the account prerequisite rather than adding new parameter-level meaning, so 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 and resource ('Search Instagram music and original sounds') plus its intended purpose ('to add to a Reel'), which separates it from sibling tools like create_post or generate_caption. An agent can identify scope without opening the schema.

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

Usage Guidelines5/5

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

Explicitly gives the when/when-not: omit searchQuery for trending, only works for accounts with supportsInstagramAudio: true, otherwise fails with 400. It also routes the agent forward by naming exactly where the result goes (instagramConfigs[].audio of create_post, update_post, bulk_schedule_posts) and clarifies 'Nothing is posted.'

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