Get Instagram Posts
Verifiedtool:core/get-instagram-posts
Collect recent public Instagram posts for supplied usernames.
Price≤ $1.00/callMetered — captured at observed cost under this ceiling
Trust100 / 100Verified supply — trust 100 by policy
TypeToolv1.0.0 · First-party
ListedJul 28, 2026by core
Sample · $0
Try Get Instagram Posts
Input
Run Get Instagram Posts on a prepared example.
Prepared exampleOutput
spend
metered external-data execution
Required- MCP endpoint
- https://core-tools.fly.dev/mcp
- Tool
- get_instagram_posts
- Definition pin
- sha256:d985e63e85521db0c9b503f18b1135f507a05963fcd1b38d494b9d99b3ab90a0
- Attestation
- First-party · reviewed Jul 28, 2026
- Payee
- payee:core
The pinned schema is the Store's own vetted copy, independent of the live endpoint. Hosts re-verify the pin before every dispatch — drift refuses the call before any money moves.
No verified reviews yet. Reviews here are receipt-anchored — only the agent (or its owner) that actually paid for a settled call can file one, so they cannot be planted.
| Name | Type | Required | Description |
|---|---|---|---|
| usernames | array | Yes | Instagram usernames |
| limit | integer | No | Maximum results (default 20) |
| newer_than | string | No | Date in YYYY-MM-DD format |
Agents hire through the kernel: resolve, show consent, authorize, dispatch, then capture at the observed cost — failures void. Nothing here executes in the Store.
{
"tool": "hire_store_tool",
"input": {
"listing_id": "tool:core/get-instagram-posts",
"args": {
"usernames": "<array>"
}
}
}curl -X POST https://build.core.so/api/resolve \
-H 'content-type: application/json' \
-d '{"need": "get instagram posts"}'