Skip to main content
Glama
deslicer

MCP Server for Splunk

update_saved_search

Update a Splunk saved search's configuration, including query, scheduling, and visibility settings, while preserving unchanged parameters for flexible search management.

Instructions

Update an existing saved search's configuration including query, scheduling, and other properties. Allows selective modification of saved search parameters while preserving unchanged settings. Supports updating search logic, time ranges, scheduling configuration, and visibility settings for flexible search management.\n\nArgs:\n name (str): Name of the saved search to update (required)\n search (str, optional): New SPL search query\n description (str, optional): New description text\n earliest_time (str, optional): New default earliest time (e.g., '-24h@h', '-7d', '2024-01-01T00:00:00')\n latest_time (str, optional): New default latest time (e.g., 'now', '@d', '2024-01-02T00:00:00')\n is_scheduled (bool, optional): Enable or disable scheduled execution\n cron_schedule (str, optional): New cron expression for scheduling\n is_visible (bool, optional): Show or hide in Splunk UI\n app (str, optional): Application context for saved search lookup\n owner (str, optional): Owner context for saved search lookup\n\nResponse Format:\nReturns dictionary with 'status', 'name', 'updated', 'changes_made', and 'updated_at' fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
searchNo
descriptionNo
earliest_timeNo
latest_timeNo
is_scheduledNo
cron_scheduleNo
is_visibleNo
appNo
ownerNo
Behavior4/5

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

Discloses partial update behavior ('selective modification while preserving unchanged settings') and lists supported update categories (search logic, scheduling, visibility). No annotations provided, so description carries full burden; it covers behavioral traits adequately, though missing authentication or permission details.

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?

Concise and well-structured: begins with clear purpose, then selective modification behavior, supported features, parameter list with format, and response format. Every sentence adds value, no redundancy.

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?

Given 10 parameters and no output schema or annotations, the description is complete. It explains what the tool does, how it behaves (partial update), details all parameters, and specifies response fields. Adequate for an update tool with moderate complexity.

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

Parameters5/5

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

Adds significant meaning beyond the input schema: includes an Args block with type, optionality, and examples for each parameter (e.g., earliest_time expects strings like '-24h@h'). Schema coverage is 0%, but description fully compensates.

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?

Clearly states 'Update an existing saved search's configuration', specifying the verb (Update) and resource (saved search). Differentiates from siblings like create_saved_search, delete_saved_search, and get_saved_search_details by focusing on modification of existing searches.

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

Usage Guidelines3/5

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

Implies usage for modifying saved searches versus creating or deleting, but does not explicitly state when to use this tool over alternatives or provide when-not-to scenarios. Lacks explicit context on prerequisites or preferred conditions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/deslicer/mcp-for-splunk'

If you have feedback or need assistance with the MCP directory API, please join our Discord server