Skip to main content
Glama

InstaVision — Instagram niche discovery

by co.instavision
OverviewDiscussionsAdmin

Launch a discovery run

launch_discovery
Destructive

Launch a discovery run. SPENDS the user's credits (real money). input.creditsCap (required, at most 500) is the most it may spend: agree it with the user first. Accounts already delivered to the user are skipped unless input.excludeSeen=false. Returns { runId }; poll get_run_status, then read get_run_results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesPlaybook slug from list_playbooks.
inputYesThe playbook's fields (list_playbooks), creditsCap and excludeSeen.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
runIdNoPass as run_id to get_run_status, get_run_results and export_run_pdf.
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / input / description
      Added value: +"The playbook's fields (list_playbooks), creditsCap and excludeSeen."
    • addedInput schema / properties / slug / description
      Added value: +"Playbook slug from list_playbooks."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "runId": {
+      "description": "Pass as run_id to get_run_status, get_run_results and export_run_pdf.",
+      "type": "string"
+    },
+    "status": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructive/non-idempotent/openWorld, but the description adds material context beyond them: the run SPENDS real money, the creditsCap bounds that spend, and already-delivered accounts are skipped unless excludeSeen=false. The cost/side-effect disclosure is exactly what an agent needs before calling an irreversible, billable operation.

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?

Four tight sentences, front-loaded with the highest-risk fact (spending credits). Every sentence carries a distinct, actionable piece of information with no filler.

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

Completeness4/5

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

An output schema exists, so return values need not be re-explained, and the description still surfaces the runId plus the polling workflow. For a complex, multi-playbook, credit-spending tool it covers the critical risks; the only omission is that input fields vary per playbook, which the schema's own description covers.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds operational meaning the schema does not: that creditsCap must be agreed with the user, and the conditional interaction where excludeSeen is bypassed for enrich-known-list. It doesn't explain the playbook-driven variation of input fields, which remains in the schema.

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+resource ('Launch a discovery run') and immediately disambiguates it from siblings by describing the downstream flow (returns runId, poll get_run_status, then read get_run_results). An agent knows exactly what this tool does and where it sits in the sequence.

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

Usage Guidelines4/5

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

Gives a clear precondition ('agree creditsCap with the user first') and names the follow-up tools, which is strong context for when to invoke it. It stops short of naming alternatives such as estimate_credits as a pre-check, so the routing guidance is clear but not exhaustive.

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

All InstaVision — Instagram niche discovery toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources