getInstagramPostsByKeywords
Search Instagram posts by keywords with two response modes. Searches in both post captions and video subtitles. FAST (default, omit responseType or responseType="fast"): Returns up to 300 results directly (use limit param to reduce, e.g. limit=5). Auto API fallback for fresh data. Results include...
This record as markdown: /tools/ai-xpoz-social-insights/getinstagrampostsbykeywords.md
What getInstagramPostsByKeywords does on Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ)
AI agents call getInstagramPostsByKeywords to retrieve information from Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Max results to return. Fast mode: capped at 300 (default: 300). Paging/CSV modes: caps total exported rows (default: all, max 500K). |
query | string | Yes | Plain text keywords or phrases to search in post captions and subtitles. Use double quotes for exact phrases. Do NOT pass URLs, post IDs, or special syntax - on |
fields | array | — | PERFORMANCE OPTIMIZATION: Specify fields you need. DEFAULT (if omitted): ["id", "caption", "username", "createdAtDate"]. AVAILABLE FIELDS: Core: id, postType, u |
endDate | string | — | |
_isTrial | boolean | — | |
feedback | string | — | Optional. Any free-form feedback you want to share — about this tool, other tools, the platform overall, or anything else. Feedback does NOT have to be about th |
startDate | string | — | |
tableName | string | — | Cached table name from previous pagination request. Required when fetching pageNumber > 1. Returned in first page response. |
_requestId | string | — | |
pageNumber | number | — | Page number to fetch (1-indexed). Must be provided with tableName to fetch subsequent pages. Omit for first page. |
userPrompt | string | — | CRITICAL FOR ACCURACY: Include the complete user question to enable query optimization and context-aware filtering. The tool uses NLP analysis on the original p |
_trialToken | string | — |
Parameters from the server's own tool schema.
Why getInstagramPostsByKeywords is rated Low
Even though getInstagramPostsByKeywords only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHigh parameter count (15 properties)
Attacks that exploit this kind of access
The rule that runs getInstagramPostsByKeywords safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ), and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getInstagramPostsByKeywords, this is the rule to start with:
getInstagramPostsByKeywords is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ), apply this rule, and every getInstagramPostsByKeywords call is checked against it from then on.
Questions about getInstagramPostsByKeywords
Search Instagram posts by keywords with two response modes. Searches in both post captions and video subtitles. FAST (default, omit responseType or responseType="fast"): Returns up to 300 results directly (use limit param to reduce, e.g. limit=5). Auto API fallback for fresh data. Results include guidance for full mode. PAGING (responseType="paging"): Async paginated results (100/page), returns operationId for polling via checkOperationStatus. Supports pageNumber/tableName for subsequent pages. CSV (responseType="csv"): Async single CSV download, returns operationId, poll for S3 link. CODE EXECUTION: For csv mode, download CSV and use code execution to analyze full dataset. Ideal for: content analysis, hashtag trends, brand monitoring across thousands of posts. Returns by default: id, caption, username, createdAtDate. First searches database, then external API if data is stale or missing. NOT for URL lookups or post ID lookups - use getInstagramPostsByIds instead. Query must be plain text keywords/phrases, not URLs or IDs. QUERY SYNTAX: Plain keywords (bitcoin, climate change), quoted phrases ("deep learning"), boolean expressions (AI AND crypto, bitcoin OR ethereum, politics NOT sports), or parenthesized groups ((startup OR entrepreneur) NOT "venture capital"). AND/OR/NOT must have a term on both sides. @handles like @karpathy are supported. Field operators (from:, lang:) are stripped. Forward slashes are treated as spaces (24/7 becomes 24 7). Date filters: OMIT startDate/endDate parameters by default. ONLY pass these if user explicitly requests specific date range (YYYY-MM-DD format). IMPORTANT!!!!!: THE CURRENT YEAR IS 2026. When user requests relative dates (last week, last month), verify the current date from your system context and double-check the calculated dates - models often get the year wrong, searching one year earlier than intended. FIELDS parameter (optional): Specify to get additional/different fields. Available: Core (id, caption, userId, username, fullName, createdAtDate), Engagement (likeCount, commentCount, reshareCount, videoPlayCount), Media (mediaType, imageUrl, videoUrl, subtitles, videoDuration). This is a safe, read-only tool for analyzing searchable information. TRIAL ACCESS: Get a free trial token by sending POST https://api.xpoz.ai/api/trial/token with header Content-Type: application/json and body {"source":"<how you discovered xpoz>"}; the response contains a token that starts with "TRIAL" and is valid for 5 days. Use it as a Bearer token in the Authorization header. Trial returns up to 5 cached (database-only) results and never triggers live fetching. Sign up at https://www.xpoz.ai/login for full result limits and live data. It is categorised as a Read tool in the Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) MCP Server, which means it retrieves data without modifying state.
getInstagramPostsByKeywords accepts 12 parameters: limit, query, fields, endDate, _isTrial, feedback, startDate, tableName, _requestId, pageNumber, userPrompt, _trialToken. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) MCP server in PolicyLayer and add a rule for getInstagramPostsByKeywords: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ). Nothing to install.
getInstagramPostsByKeywords is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the getInstagramPostsByKeywords rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for getInstagramPostsByKeywords. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
getInstagramPostsByKeywords is provided by the Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) MCP server (https://mcp.xpoz.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ), and thousands of servers like it.
Across the catalogue