Skip to main content
Glama

Metadata MCP Connector

by io.metadata.mcp-server
OverviewDiscussionsAdmin

List All Budget Groups

list_budget_groups
Read-only

Browse and list all available budget groups in the Metadata platform with customizable sorting.

            Default results include both switched-on and switched-off groups. Omit status for
            inventory and spreadsheet updates; use status=true or status=false only when the user
            requests that switch state. Reading a switched-off group does not switch it on.
            Paginate through totalPages before declaring a named group missing.

            KEYWORDS: budget, group, list, all, browse, spending, allocation, optimization, overview

            **DIFFERENCE FROM get_budget_group:**
            - get_budget_group: Searches for ONE specific group BY NAME (requires group name input)
            - list_budget_groups: Returns a paginated list of groups (supports flexible sorting)

            USE THIS TOOL WHEN THE USER ASKS:
            - "Show me all budget groups" or "List all budget groups"
            - "What budget groups do we have?"
            - "Display all available groups"
            - "Show groups sorted by [metric]"
            - "Which groups have the highest budget?"
            - "Show groups by leads generated"
            - "List groups sorted by CPL"
            - "Order groups by spending"

            DO NOT USE if the user:
            - Asks for details about a SPECIFIC group by name → use get_budget_group instead
            - Wants to find a group by name → use get_budget_group instead
            - Says "Find the [specific name] group" → use get_budget_group instead

            SORTING OPTIONS:
            You can sort by any of these fields (default: totalActiveExperiments descending):
            - totalActiveExperiments, monthlyCap, averageDailyBudgetPerExperiment
            - spent, totalBudget, endDate, startDate, leads, cpl

            SORT ORDER:
            - asc: Ascending order (lowest to highest, oldest to newest)
            - desc: Descending order (highest to lowest, newest to oldest) [DEFAULT]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination (0-based). Default: 0
sizeNoNumber of results per page. Default: 10
statusNoOptional switch-state filter: true for switched-on groups, false for switched-off groups. Omit to include both.
sort_byNoField to sort budget groups by. Default: totalActiveExperiments
sort_orderNoSort order - 'asc' (ascending) or 'desc' (descending). Default: desc

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / status
      Added value: +{
+  "description": "Optional switch-state filter: true for switched-on groups, false for switched-off groups. Omit to include both.",
+  "type": "boolean"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare the read-only, non-destructive, closed-world profile, but the description adds non-obvious behavior: reading a switched-off group does not switch it on, the default result set spans both switch states, and results must be paginated through totalPages before concluding a group is missing. These are genuine side-effect and completeness disclosures beyond the annotations.

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

Conciseness3/5

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

Front-loaded and well-sectioned, but bloated: three separate DO NOT USE bullets all restate the same get_budget_group redirect, the SORTING OPTIONS/SORT ORDER blocks duplicate the schema enums verbatim, and the KEYWORDS line adds no selection value. Content earns its place individually, but the redundancy costs it.

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?

No output schema exists, and the description partly compensates by naming pagination fields (totalPages) and the shape of results. Filtering, sorting, and routing are all covered; a fuller return-shape sketch would make it complete.

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?

Schema coverage is 100% and the enum lists already document sort fields, so baseline is 3; the description goes further by stating the default sort (totalActiveExperiments descending), spelling out asc/desc semantics, and giving the conditional rule for when to pass status at all.

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+resource ('list all available budget groups') with scope (paginated, sortable) and explicitly contrasts itself against get_budget_group in a dedicated DIFFERENCE section. An agent can distinguish it from siblings without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit trigger phrases ('Show me all budget groups'), explicit exclusions routed to get_budget_group, and a conditional rule for the status filter (omit for inventory/spreadsheet updates; set only on explicit user request). When/when-not/alternative are all covered.

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

All Metadata MCP Connector 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