InstaBids

This connector has been deprecated

Duplicate listing. The current InstaBids connector is https://glama.ai/mcp/connectors/ai.instabids/instabids

How InstaBids works

how_instabids_works

Read-onlyIdempotent

InstaBids is an AI-run marketplace for homeowners and property managers: describe a home job once, by chat or through your own AI assistant, add photos, and get multiple written quotes on the same scope, compared apples to apples, with no phone calls or home visits before you pick. Learn the homeowner steps, homeowner cost and contact privacy.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "how_instabids_works"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`steps`	Yes
`guidance`	Yes
`nextStep`	No
`sourceUrl`	Yes
`homeownerFee`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026
- addedOutput schema / properties / nextStep
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedOct 30, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "guidance": {
+      "type": "string"
+    },
+    "homeownerFee": {
+      "type": "string"
+    },
+    "sourceUrl": {
+      "format": "uri",
+      "pattern": "^https://",
+      "type": "string"
+    },
+    "steps": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "heading": {
+            "type": "string"
+          },
+          "text": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "heading",
+          "text"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "homeownerFee",
+    "steps",
+    "guidance",
+    "sourceUrl"
+  ],
+  "type": "object"
+}

First observedOct 30, 2026

TDQS

B3.3/5.0

Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world tool. The description adds useful domain context about what InstaBids is, but it does not disclose additional behavior such as whether the returned content is static documentation, how current it is, or any rate limits.

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?

The description is only two sentences and contains no obvious repetition. The first sentence is somewhat long and marketing-oriented, but it provides context before the second sentence states the covered topics.

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

Completeness3/5

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

For a zero-parameter informational tool with an output schema, the description covers the main content areas but remains somewhat ambiguous about whether it returns static documentation and how it differs from the contractor sibling. It is adequate, but not fully complete for an agent deciding between informational tools.

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?

The tool has zero parameters and the input schema is empty, so the baseline score is 4. There are no parameter meanings for the description to clarify beyond what the schema already shows.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the subject (InstaBids marketplace) and the topics covered (homeowner steps, homeowner cost, contact privacy), so an agent can tell it is an informational tool. It does not explicitly contrast itself with the contractor-focused sibling, which keeps it from a 5.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance. The phrase 'Learn the homeowner steps...' implies an educational purpose, but the description never says when to call this tool instead of job_guidance, how_contractors_join, or other siblings.

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

All InstaBids tools Inspect

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

Need Help?