AlphaWeb

glowups_get

Read-only

Read untrusted audit/mockups/progress free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace": "<workspace>"
    },
    "name": "glowups_get"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	No
`scope`	No
`cursor`	No
`run_id`	No
`section`	No
`asset_ids`	No
`report_id`	No
`workspace`	Yes
`glowup_ref`	No
`image_detail`	No
`wait_seconds`	No
`recommendation_id`	No
`prospect_session_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 1, 2026

addedInput schema / properties / asset_ids

Added value: +{
+  "items": {
+    "maxLength": 200,
+    "type": "string"
+  },
+  "maxItems": 20,
+  "type": "array"
+}

addedInput schema / properties / image_detail

Added value: +{
+  "enum": [
+    "overview",
+    "full"
+  ],
+  "type": "string"
+}

addedInput schema / properties / prospect_session_id

Added value: +{
+  "format": "uuid",
+  "type": "string"
+}

addedInput schema / properties / recommendation_id

Added value: +{
+  "maxLength": 200,
+  "type": "string"
+}

addedInput schema / properties / report_id

Added value: +{
+  "format": "uuid",
+  "type": "string"
+}

addedInput schema / properties / scope

Added value: +{
+  "enum": [
+    "workspace",
+    "personal_unattached"
+  ],
+  "type": "string"
+}

First observedOct 23, 2026

TDQS

D1.8/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds a vague 'untrusted' trust warning, but says nothing about pagination, wait_seconds behavior, result shape, or what 'free' means, leaving important behavioral traits unclear.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is short, but it is cryptic rather than concise: 'untrusted audit/mockups/progress free' does not front-load a clear resource or operation. It is under-specified for a 14-parameter tool.

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

Completeness1/5

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

This is a complex read tool with 14 parameters, no output schema, and schema coverage of 0%. The description is far too sparse to help an agent understand what is returned, how to use the many filters, or how it relates to sibling GlowUp tools.

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

Parameters1/5

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

Schema description coverage is 0% across 14 parameters, including scope, section, cursor, run_id, image_detail, and wait_seconds. The description provides no parameter explanations or usage constraints, so it does not compensate for the schema gap at all.

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

Purpose2/5

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

The description uses a read verb and mentions audit/mockups/progress, but it never clearly names the GlowUps resource or explains the dangling word 'free'. It does not distinguish this tool from nearby siblings such as glowup_actions_get or glowup_build_open.

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 guidance about when to use this tool, when to use an alternative, or what prerequisites are required. The only possible signal is the word 'untrusted', which does not tell an agent how to decide between this and sibling read tools.

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

All AlphaWeb 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?