Gumloop MCP Server

Search Company Brain

search_brain

Destructive

Run a hybrid semantic and keyword search across indexed company knowledge to return ranked, cited snippets scoped to your access.

Instructions

Run a hybrid (semantic + keyword) search across the knowledge sources indexed in your Company Brain and return the most relevant, ranked snippets with citations.

Results are scoped to what the authenticated user can see: personal sources, plus any team and organization sources shared with them. Requires the Brain feature, which is available on the Pro and Enterprise plans. Each search consumes Gumloop credits. Explicit confirmation is required for this credit-consuming Brain search.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of results to return.
`query`	No	The natural-language search query.
`account`	No	Named private Gumloop account; selects private credentials and user/team identity.
`confirm`	No	Set true only when the user asked for exactly this action.
`payload`	No	Complete JSON request body instead of body flags. Preserves current endpoint fields and values.
`source_type`	No
`payload_file`	No	Regular local JSON body file, at most 5 MB. Cannot be mixed with body flags or payload.

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedv3.0.0Oct 5, 2026

addedInput schema / $defs / source_type

Added value: +{
+  "description": "Restrict results to specific source types. Omit to search every source you can access. Valid values: `notion`, `google_drive`, `slack`, `github`, `confluence`, `direct_file_uploads`, `gumloop_artifacts`.\n",
+  "items": {
+    "enum": [
+      "notion",
+      "google_drive",
+      "slack",
+      "github",
+      "confluence",
+      "direct_file_uploads",
+      "gumloop_artifacts"
+    ],
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": [
+    "array",
+    "null"
+  ]
+}

changedInput schema / properties / confirm / description

Previous value: -"Must be true for this exact requested account change, agent/flow execution, upload or deletion."New value: +"Set true only when the user asked for exactly this action."

addedInput schema / properties / payload / properties / source_type / $ref
```
Added value: +"#/$defs/source_type"
```

removedInput schema / properties / payload / properties / source_type / description

Removed value: -"Restrict results to specific source types. Omit to search every source you can access. Valid values: `notion`, `google_drive`, `slack`, `github`, `confluence`, `direct_file_uploads`, `gumloop_artifacts`.\n"

removedInput schema / properties / payload / properties / source_type / items

Removed value: -{
-  "enum": [
-    "notion",
-    "google_drive",
-    "slack",
-    "github",
-    "confluence",
-    "direct_file_uploads",
-    "gumloop_artifacts"
-  ],
-  "type": "string"
-}

removedInput schema / properties / payload / properties / source_type / minItems
```
Removed value: -1
```
removedInput schema / properties / payload / properties / source_type / type
```
Removed value: -[
-  "array",
-  "null"
-]
```
addedInput schema / properties / source_type / $ref
```
Added value: +"#/$defs/source_type"
```

removedInput schema / properties / source_type / description

Removed value: -"Restrict results to specific source types. Omit to search every source you can access. Valid values: `notion`, `google_drive`, `slack`, `github`, `confluence`, `direct_file_uploads`, `gumloop_artifacts`.\n"

removedInput schema / properties / source_type / items

Removed value: -{
-  "enum": [
-    "notion",
-    "google_drive",
-    "slack",
-    "github",
-    "confluence",
-    "direct_file_uploads",
-    "gumloop_artifacts"
-  ],
-  "type": "string"
-}

removedInput schema / properties / source_type / minItems
```
Removed value: -1
```
removedInput schema / properties / source_type / type
```
Removed value: -[
-  "array",
-  "null"
-]
```

First observedv2.0.1Oct 3, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations mark this as non-read-only and destructive, and the description supplies the reason an agent needs to be careful: it consumes Gumloop credits and demands explicit confirmation. That is genuine context beyond the annotation flags. It still does not describe result volume, ranking behavior, or pagination, so it stops short of full disclosure.

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-loads the core action and result format, then layers scoping, prerequisites, and cost in descending order of importance. Four sentences is slightly more than needed, and the inline documentation link is of marginal value to an agent, but nothing is redundant.

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?

For a 7-parameter tool with a nested payload object and no output schema, the description covers purpose, access scoping, plan gating, credit cost, and the confirmation gate. It leaves the payload/payload_file alternates and account semantics to the schema, which is acceptable given the high coverage.

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 86%, so the schema already documents query, limit, source_type, account, confirm, and payload. The description adds only that the query is hybrid semantic+keyword in nature, which mildly enriches the query parameter but does not explain the confirm or payload flags. Baseline 3 is appropriate.

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 (search), the mechanism (hybrid semantic + keyword), the resource (knowledge sources in the Company Brain), and the return shape (ranked snippets with citations). It is clearly distinguishable from siblings like list_brain_sources or get_brain_source, which browse rather than query.

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 real conditions: results are scoped to what the authenticated user can see, the Brain feature must exist (Pro/Enterprise only), each call consumes credits, and explicit confirmation is required. It does not name an alternative tool for browsing indexed sources, so routing is implied rather than explicit.

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

Deploy Server

Search Company Brain

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools