Skip to main content
Glama
darrenjrobinson

Entra News MCP Server

list_issues

Browse Entra.news archive issues with filtering by year and month to discover available content before retrieving specific issues or performing searches.

Instructions

Browse the Entra.news archive with optional year/month filtering. Returns a list of issues with title, date, and URL. Use this to discover what issues exist before using get_issue or search_entra_news.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNoFilter by year (e.g. 2024)
monthNoFilter by month number 1–12 (e.g. 3 for March). Requires year.
limitNoMaximum issues to return (default: 50)
offsetNoPagination offset (default: 0)

Implementation Reference

  • The handler function `handleListIssues` executes the logic to fetch and format the issue list.
    export function handleListIssues(args: ListIssuesArgs): string {
      const { year, month, limit, offset } = args;
    
      const issues = listIssues({ year, month, limit, offset });
      const meta = getDbMeta();
    
      if (issues.length === 0) {
        const filter = [year, month ? MONTH_NAMES[month - 1] : null].filter(Boolean).join(' ');
        return `No issues found${filter ? ` for ${filter}` : ''}.`;
      }
    
      const filterDesc = [
        month ? MONTH_NAMES[month - 1] : null,
        year ? String(year) : null,
      ]
        .filter(Boolean)
        .join(' ');
    
      const totalNote = meta.issue_count ? ` (${meta.issue_count} total in archive)` : '';
      const paginationNote =
        offset > 0 || issues.length === limit
          ? `\nShowing ${offset + 1}–${offset + issues.length}${totalNote}`
          : `\n${issues.length} issue(s)${totalNote}`;
    
      const header = `## Entra.news Archive${filterDesc ? ` — ${filterDesc}` : ''}${paginationNote}\n\n`;
      const lastUpdated = meta.last_updated
        ? `*Last updated: ${new Date(meta.last_updated).toLocaleDateString('en-US', { year: 'numeric', month: 'long', day: 'numeric' })}*\n\n`
        : '';
    
      const rows = issues.map(formatIssueRow).join('\n');
      return `${header}${lastUpdated}\`\`\`\n${rows}\n\`\`\``;
    }
  • The Zod schema `listIssuesSchema` defines input validation for the `list_issues` tool.
    export const listIssuesSchema = z.object({
      year: z
        .number()
        .int()
        .min(2023)
        .max(2030)
        .optional()
        .describe('Filter by year (e.g. 2024)'),
      month: z
        .number()
        .int()
        .min(1)
        .max(12)
        .optional()
        .describe('Filter by month number (1–12). Requires year to be set.'),
      limit: z
        .number()
        .int()
        .min(1)
        .max(200)
        .default(50)
        .describe('Maximum issues to return'),
      offset: z
        .number()
        .int()
        .min(0)
        .default(0)
        .describe('Pagination offset'),
    });
  • src/server.ts:66-94 (registration)
    Registration of the `list_issues` tool in `src/server.ts`.
      name: 'list_issues',
      description:
        'Browse the Entra.news archive with optional year/month filtering. ' +
        'Returns a list of issues with title, date, and URL. ' +
        'Use this to discover what issues exist before using get_issue or search_entra_news.',
      inputSchema: {
        type: 'object',
        properties: {
          year: {
            type: 'number',
            description: 'Filter by year (e.g. 2024)',
          },
          month: {
            type: 'number',
            description: 'Filter by month number 1–12 (e.g. 3 for March). Requires year.',
          },
          limit: {
            type: 'number',
            description: 'Maximum issues to return (default: 50)',
            default: 50,
          },
          offset: {
            type: 'number',
            description: 'Pagination offset (default: 0)',
            default: 0,
          },
        },
      },
    },
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It compensates by disclosing the return structure ('Returns a list of issues with title, date, and URL') which is critical without an output schema. It notes the optional filtering behavior. Does not explicitly state read-only nature, though implied by 'Browse'.

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?

Three sentences with zero waste: (1) states purpose and filtering, (2) discloses return values, (3) provides workflow guidance. Efficiently front-loaded and appropriately sized for the tool's complexity.

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 4 optional parameters with full schema coverage and no output schema, the description adequately covers what is returned. The workflow context with sibling tools completes the picture. Minor gap: could explicitly mention pagination behavior, though offset/limit parameters are self-documenting.

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%, providing detailed descriptions for year, month, limit, and offset. The description mentions 'optional year/month filtering' which reinforces the schema but does not add syntax details beyond what the schema already provides. Baseline 3 is appropriate given comprehensive schema coverage.

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 uses a specific verb ('Browse') and resource ('Entra.news archive') and explicitly distinguishes from siblings by stating this is for discovering what issues exist before using get_issue or search_entra_news.

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?

Provides explicit workflow guidance: 'Use this to discover what issues exist before using get_issue or search_entra_news.' This clearly sequences the tool's use relative to alternatives and defines its role in the discovery phase.

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/darrenjrobinson/EntraNewsMCPServer'

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