Skip to main content
Glama
its-qusai-nasr

Jira Admin MCP Server

jira_filters_search

Read-only

Search saved JQL filters by name or owner account ID to locate and manage filters efficiently.

Instructions

Search for saved JQL filters.

Returns: {total, filters: [{id, name, jql, owner, favourite_count}]}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filter_nameNoFilter by name substring
owner_account_idNoFilter by owner's account ID
max_resultsNoMax results. Default: 25

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description adds no further behavioral traits. It is consistent with annotations but does not disclose additional details like pagination or auth requirements.

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?

The description is extremely concise: one line of purpose plus return format. Every sentence is informative with no waste.

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?

Given the output schema is described in the description, and the tool is simple with few parameters, the description is sufficiently complete. It covers the return structure and filtering capabilities.

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 parameters. The description does not add meaning beyond what is in the schema, meeting the baseline.

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?

The description clearly states the verb 'Search' and the resource 'saved JQL filters', and distinguishes from sibling tools like jira_filters_get (retrieve a specific filter) and jira_filters_create.

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?

No guidance on when to use this tool versus alternatives such as jira_filters_get or jira_issues_search. The description does not specify context or exclusions.

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/its-qusai-nasr/jira-admin-mcp'

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