Skip to main content
Glama

More Good Reviews

by com.moregoodreviews
OverviewDiscussionsAdmin

Create Tag

createTag

Create Tag

Create a project tag for customer or review organization.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesDisplay name for this tag.
colorNoHex color associated with this tag. Accepts #RGB or #RRGGBB, at most 30 characters.
spriteNoFont Awesome icon CSS classes for this tag. Font Awesome icon: two CSS class names as used with Font Awesome Web Fonts / classic CSS (not SVG/React props). Format is a style prefix (`fab`, `fad`, `fak`, `fal`, `far`, `fas`, or `fat`), one ASCII space, then an icon slug starting with `fa-` (lowercase letters and digits, hyphen-separated words). Examples: `fab fa-google`, `fas fa-star`. On write, omit, send null, or whitespace-only to clear. Font Awesome 6 semantic pairs such as `fa-solid fa-star` are not accepted; use `fas fa-star` instead. Accepts at most 50 characters.
contextNoResource type this tag applies to.
has_ai_taggingNoWhether AI tagging is enabled for this tag.
ai_instructionsNoInstructions used by AI tagging for review tags.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNoApplication-level status code returned by this API.
dataNoProject tag metadata.
successNoIndicates whether the request completed successfully.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / color / description
      Previous value: -"Hex color associated with this tag. Accepts"New value: +"Hex color associated with this tag. Accepts #RGB or #RRGGBB, at most 30 characters."
    • changedOutput schema / properties / data / anyOf
      Previous value: -[
-  {
-    "additionalProperties": {},
-    "properties": {
-      "ai_instructions": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "Instructions used by AI tagging for review tags."
-      },
-      "color": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "Hex color associated with this tag. Accepts"
-      },
-      "context": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "Resource type this tag applies to."
-      },
-      "has_ai_tagging": {
-        "anyOf": [
-          {
-            "type": "boolean"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "Whether AI tagging is enabled for this tag."
-      },
-      "id": {
-        "anyOf": [
-          {
-            "maximum": 9007199254740991,
-            "minimum": -9007199254740991,
-            "type": "integer"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "Unique numeric identifier for this tag."
-      },
-      "name": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "Display name for this tag."
-      },
-      "slug": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "URL-friendly identifier for this tag."
-      },
-      "sprite": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "Font Awesome icon: two CSS class names as used with Font Awesome Web Fonts / classic CSS (not SVG/React props). Format is a style prefix (`fab`, `fad`, `fak`, `fal`, `far`, `fas`, or `fat`), one ASCII space, then an icon slug starting with `fa-` (lowercase letters and digits, hyphen-separated words). Examples: `fab fa-google`, `fas fa-star`. On write, omit, send null, or whitespace-only to clear. Font Awesome 6 semantic pairs such as `fa-solid fa-star` are not accepted; use `fas fa-star` instead."
-      },
-      "uuid": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "Stable UUID for this tag."
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "ai_instructions": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Instructions used by AI tagging for review tags."
+      },
+      "color": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Hex color associated with this tag. Accepts #RGB or #RRGGBB, at most 30 characters."
+      },
+      "context": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Resource type this tag applies to."
+      },
+      "has_ai_tagging": {
+        "anyOf": [
+          {
+            "type": "boolean"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Whether AI tagging is enabled for this tag."
+      },
+      "id": {
+        "anyOf": [
+          {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Unique numeric identifier for this tag."
+      },
+      "name": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Display name for this tag."
+      },
+      "slug": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "URL-friendly identifier for this tag."
+      },
+      "sprite": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Font Awesome icon: two CSS class names as used with Font Awesome Web Fonts / classic CSS (not SVG/React props). Format is a style prefix (`fab`, `fad`, `fak`, `fal`, `far`, `fas`, or `fat`), one ASCII space, then an icon slug starting with `fa-` (lowercase letters and digits, hyphen-separated words). Examples: `fab fa-google`, `fas fa-star`. On write, omit, send null, or whitespace-only to clear. Font Awesome 6 semantic pairs such as `fa-solid fa-star` are not accepted; use `fas fa-star` instead."
+      },
+      "uuid": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Stable UUID for this tag."
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that: no statement about name uniqueness, duplicate-creation behavior, permission requirements, or project scoping. It is not contradictory, just empty on behavior.

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?

Two short lines with no filler and the core action front-loaded. Minor redundancy: the first line merely restates the title, so one of the two sentences carries almost no information.

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?

An output schema exists so return values need not be explained, and annotations cover safety. However, for a creation tool with six parameters and AI-tagging options, the description omits anything about scope, uniqueness constraints, or how the new tag relates to existing tags, leaving the definition only minimally viable.

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 100%, so the schema already documents all six parameters in detail (color hex format, sprite CSS class rules, context enum values). The description's phrase 'for customer or review organization' loosely gestures at the context parameter but adds no syntax or format detail. Baseline 3 is appropriate.

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?

States a specific verb and resource ('Create a project tag') plus the organizational scope ('for customer or review organization'), which maps to the context enum. It is distinguishable from createCustomer/createReview and from updateTag/deleteTag, though it never names those siblings.

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 when-to-use guidance, no mention of prerequisites, and no routing to alternatives such as updateTag when the tag already exists. The reader must infer usage entirely from the tool name.

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

All More Good Reviews 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