Ogury MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OGURY_CLIENT_ID | Yes | Your Ogury API client ID for authentication | |
| OGURY_CLIENT_SECRET | Yes | Your Ogury API client secret for authentication |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_campaign_detailsC | Get campaign performance details by campaign ID |
| get_campaigns_reportC | Get campaign performance report with flexible filtering |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have overlapping purposes, as both retrieve campaign performance data, which could cause confusion for an agent. While 'get_campaign_details' targets a specific campaign by ID and 'get_campaigns_report' offers flexible filtering, the descriptions do not clearly differentiate their use cases, leading to potential misselection.
The tool names follow a consistent verb_noun pattern with 'get_campaign_details' and 'get_campaigns_report', both using snake_case and starting with 'get'. This predictability makes it easy for agents to understand the naming convention.
With only 2 tools, the server feels thin and under-scoped for a campaign management domain, as it lacks essential operations like creating, updating, or deleting campaigns. This limited set may hinder agent workflows and suggests an incomplete implementation.
The tool surface is severely incomplete for campaign management, covering only read operations (details and reports) without any create, update, or delete capabilities. This creates significant gaps that will likely cause agent failures in handling full campaign lifecycles.