gemini-media-mcp

Overview Schema Source Related Servers Discussions Admin

Get configuration

get_config

Read-onlyIdempotent

Reveals the active backend, output directory, default models, budgets, input-file policy, and configuration warnings so you can troubleshoot credentials or missing files.

Instructions

Show the active backend and how it was chosen, output directory, default models, budgets, input-file policy and configuration warnings. Use it to troubleshoot credentials or missing files.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`budget`	Yes
`backend`	Yes
`project`	No
`version`	Yes
`authMode`	Yes
`defaults`	Yes
`httpAddr`	No	Address the HTTP transport listens on
`location`	No
`stateDir`	Yes
`warnings`	No
`outputDir`	Yes
`transport`	Yes
`configFile`	No
`catalogFile`	No
`inputPolicy`	Yes
`backendReason`	Yes
`catalogVersion`	Yes
`inlinePreviews`	Yes
`settingSources`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed18 schema fields changedv1.1.0Oct 14, 2026

addedOutput schema / properties / authMode
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / backendReason
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / budget

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "confirmAboveUsd": {
+      "type": "number"
+    },
+    "dailyUsd": {
+      "type": "number"
+    },
+    "monthlyUsd": {
+      "type": "number"
+    },
+    "sessionUsd": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "sessionUsd",
+    "dailyUsd",
+    "monthlyUsd",
+    "confirmAboveUsd"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / catalogFile
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / catalogVersion
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / configFile
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / defaults

Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

addedOutput schema / properties / httpAddr

Added value: +{
+  "description": "Address the HTTP transport listens on",
+  "type": "string"
+}

addedOutput schema / properties / inlinePreviews
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / inputPolicy
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / location
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / project
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / settingSources

Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "type": "object"
+}

addedOutput schema / properties / stateDir
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / transport
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / version
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / warnings

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "backend",
-  "outputDir"
-]New value: +[
+  "version",
+  "backend",
+  "authMode",
+  "backendReason",
+  "transport",
+  "outputDir",
+  "stateDir",
+  "catalogVersion",
+  "defaults",
+  "budget",
+  "inputPolicy",
+  "inlinePreviews"
+]

First observedApr 15, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so safety is covered structurally. The description goes beyond them by describing the informational surface returned (backend selection rationale, policy, warnings) and the diagnostic intent (credentials/missing files), which is genuine extra context for an inspection tool.

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?

Two sentences, zero filler. The content enumeration comes first and the use case second, so the agent gets the what before the when.

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

Completeness5/5

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

With an output schema present, return-value detail is unnecessary in the description, and the zero-parameter, read-only profile needs no further caveats. Content and purpose are both covered, so nothing an agent needs in order to call it correctly is missing.

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 takes zero parameters and the schema is a closed empty object, so there is nothing parameter-wise for the description to explain. Baseline 4 applies for a no-parameter tool.

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 ('Show') and resource (configuration) and then enumerates exactly what it reveals: active backend and its selection rationale, output directory, default models, budgets, input-file policy, and warnings. Nothing in the sibling list (media generation, usage, model listing) overlaps with this, so an agent can select it without ambiguity.

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 concrete situation to reach for it: 'Use it to troubleshoot credentials or missing files.' That is a clear when-to-use signal, but no alternatives are named or excluded (e.g., versus get_usage or list_models for related diagnostics).

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

Deploy Server