Skip to main content
Glama

list-milestones

Retrieve milestones from Float using filters for project, phase, status, date range, priority, and pagination to get targeted results.

Instructions

List all milestones with optional filtering by project, phase, status, or date range

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idNoFilter by project ID
phase_idNoFilter by phase ID
statusNoFilter by milestone status (numeric)
completedNoFilter by completion status (0=not completed, 1=completed)
activeNoFilter by active status (0=archived, 1=active)
start_dateNoFilter by start date (YYYY-MM-DD format)
end_dateNoFilter by end date (YYYY-MM-DD format)
date_fromNoFilter milestones from this date (YYYY-MM-DD format)
date_toNoFilter milestones to this date (YYYY-MM-DD format)
priorityNoFilter by priority level (1-5)
created_byNoFilter by creator user ID
pageNoPage number for pagination
per-pageNoNumber of items per page (max 200)

Implementation Reference

  • The 'list-milestones' tool handler function. Defined via createTool with name 'list-milestones', description about listing milestones, input schema (Zod) for filtering parameters, and an async handler that calls floatApi.getPaginated('/milestones', params, milestonesResponseSchema).
    export const listMilestones = createTool(
      'list-milestones',
      'List all milestones with optional filtering by project, phase, status, or date range',
      z.object({
        project_id: z.number().optional().describe('Filter by project ID'),
        phase_id: z.number().optional().describe('Filter by phase ID'),
        status: z.number().optional().describe('Filter by milestone status (numeric)'),
        completed: z
          .number()
          .optional()
          .describe('Filter by completion status (0=not completed, 1=completed)'),
        active: z.number().optional().describe('Filter by active status (0=archived, 1=active)'),
        start_date: z.string().optional().describe('Filter by start date (YYYY-MM-DD format)'),
        end_date: z.string().optional().describe('Filter by end date (YYYY-MM-DD format)'),
        date_from: z
          .string()
          .optional()
          .describe('Filter milestones from this date (YYYY-MM-DD format)'),
        date_to: z.string().optional().describe('Filter milestones to this date (YYYY-MM-DD format)'),
        priority: z.number().optional().describe('Filter by priority level (1-5)'),
        created_by: z.number().optional().describe('Filter by creator user ID'),
        page: z.number().optional().describe('Page number for pagination'),
        'per-page': z.number().optional().describe('Number of items per page (max 200)'),
      }),
      async (params) => {
        const response = await floatApi.getPaginated('/milestones', params, milestonesResponseSchema);
        return response;
      }
    );
  • Input schema for list-milestones. Zod object with optional fields: project_id, phase_id, status, completed, active, start_date, end_date, date_from, date_to, priority, created_by, page, 'per-page'.
    z.object({
      project_id: z.number().optional().describe('Filter by project ID'),
      phase_id: z.number().optional().describe('Filter by phase ID'),
      status: z.number().optional().describe('Filter by milestone status (numeric)'),
      completed: z
        .number()
        .optional()
        .describe('Filter by completion status (0=not completed, 1=completed)'),
      active: z.number().optional().describe('Filter by active status (0=archived, 1=active)'),
      start_date: z.string().optional().describe('Filter by start date (YYYY-MM-DD format)'),
      end_date: z.string().optional().describe('Filter by end date (YYYY-MM-DD format)'),
      date_from: z
        .string()
        .optional()
        .describe('Filter milestones from this date (YYYY-MM-DD format)'),
      date_to: z.string().optional().describe('Filter milestones to this date (YYYY-MM-DD format)'),
      priority: z.number().optional().describe('Filter by priority level (1-5)'),
      created_by: z.number().optional().describe('Filter by creator user ID'),
      page: z.number().optional().describe('Page number for pagination'),
      'per-page': z.number().optional().describe('Number of items per page (max 200)'),
    }),
  • Import of listMilestones from milestones.ts and its registration in the legacyTools array at line 238, which are then exported as part of the tools array.
      listMilestones,
      getMilestone,
      createMilestone,
      updateMilestone,
      deleteMilestone,
      getProjectMilestones,
      getUpcomingMilestones,
      getOverdueMilestones,
      completeMilestone,
      getMilestoneReminders,
    } from './project-management/milestones.js';
    import {
      listPhases,
      getPhase,
      createPhase,
      updatePhase,
      deletePhase,
      listPhasesByProject,
      getPhasesByDateRange,
      getActivePhases,
      getPhaseSchedule,
    } from './project-management/phases.js';
    import {
      listProjectTasks,
      getProjectTask,
      createProjectTask,
      updateProjectTask,
      deleteProjectTask,
      getProjectTasksByProject,
      getProjectTasksByPhase,
      bulkCreateProjectTasks,
      reorderProjectTasks,
      archiveProjectTask,
      getProjectTaskDependencies,
    } from './project-management/project-tasks.js';
    
    // Time management tools
    import {
      listTimeOff,
      getTimeOff,
      createTimeOff,
      updateTimeOff,
      deleteTimeOff,
      bulkCreateTimeOff,
      approveTimeOff,
      rejectTimeOff,
      listTimeOffTypes,
      getTimeOffCalendar,
      getPersonTimeOffSummary,
    } from './time-management/timeoff.js';
    import {
      listTimeOffTypes as listTimeOffTypesConfig,
      getTimeOffType,
      createTimeOffType,
      updateTimeOffType,
      deleteTimeOffType,
    } from './time-management/timeoff-types.js';
    import {
      listPublicHolidays,
      getPublicHoliday,
      createPublicHoliday,
      updatePublicHoliday,
      deletePublicHoliday,
    } from './time-management/public-holidays.js';
    import {
      listTeamHolidays,
      getTeamHoliday,
      createTeamHoliday,
      updateTeamHoliday,
      deleteTeamHoliday,
      listTeamHolidaysByDepartment,
      listTeamHolidaysByDateRange,
      listRecurringTeamHolidays,
      getUpcomingTeamHolidays,
    } from './time-management/team-holidays.js';
    import {
      listLoggedTime,
      getLoggedTime,
      createLoggedTime,
      updateLoggedTime,
      deleteLoggedTime,
      bulkCreateLoggedTime,
      getPersonLoggedTimeSummary,
      getProjectLoggedTimeSummary,
      getLoggedTimeTimesheet,
      getBillableTimeReport,
    } from './time-management/logged-time.js';
    
    // Reporting tools
    import {
      getTimeReport,
      getProjectReport,
      getPeopleUtilizationReport,
    } from './reporting/reports.js';
    
    // Legacy tools export (preserved for backward compatibility)
    export const legacyTools = [
      // Core entity tools
      listPeople,
      getPerson,
      createPerson,
      updatePerson,
      deletePerson,
      listDepartments,
      getDepartment,
      createDepartment,
      updateDepartment,
      deleteDepartment,
      listStatuses,
      getStatus,
      createStatus,
      updateStatus,
      deleteStatus,
      getDefaultStatus,
      setDefaultStatus,
      getStatusesByType,
      listRoles,
      getRole,
      createRole,
      updateRole,
      deleteRole,
      getRolesByPermission,
      getRolePermissions,
      updateRolePermissions,
      getRoleHierarchy,
      checkRoleAccess,
      listAccounts,
      getAccount,
      updateAccount,
      manageAccountPermissions,
      createAccount,
      deactivateAccount,
      reactivateAccount,
      getCurrentAccount,
      updateAccountTimezone,
      setAccountDepartmentFilter,
      bulkUpdateAccountPermissions,
    
      // Project management tools
      listProjects,
      getProject,
      createProject,
      updateProject,
      deleteProject,
      listTasks,
      getTask,
      createTask,
      updateTask,
      deleteTask,
      listClients,
      getClient,
      createClient,
      updateClient,
      deleteClient,
      listAllocations,
      getAllocation,
      createAllocation,
      updateAllocation,
      deleteAllocation,
      listMilestones,
      getMilestone,
      createMilestone,
      updateMilestone,
      deleteMilestone,
      getProjectMilestones,
      getUpcomingMilestones,
      getOverdueMilestones,
      completeMilestone,
      getMilestoneReminders,
      listPhases,
  • The getPaginated helper method on FloatApi class that list-milestones uses to make the actual API call to /milestones endpoint.
    async getPaginated<T>(
      url: string,
      params?: Record<string, unknown>,
      schema?: z.ZodType<T[]>,
      format: ResponseFormat = 'json'
    ): Promise<T[]> {
      const queryString = this.buildQueryParams({
        ...params,
        'per-page': params?.['per-page'] || 200, // Float API max page size
      });
    
      return this.get<T[]>(`${url}${queryString}`, schema, format);
    }
  • The milestoneSchema Zod definition defining the structure of milestone objects returned by the API.
    export const milestoneSchema = z.object({
      milestone_id: z.number().optional(), // Float API uses milestone_id, not id
      project_id: z.number().optional(),
      phase_id: z.number().nullable().optional(),
      name: z.string(),
      description: z.string().nullable().optional(),
      date: z.string().nullable().optional(), // ISO date format (YYYY-MM-DD)
      start_date: z.string().nullable().optional(),
      end_date: z.string().nullable().optional(),
      status: z.number().nullable().optional(), // Float API uses numeric status codes
      created: z.string().nullable().optional(), // Float API uses 'created', not 'created_at'
      modified: z.string().nullable().optional(), // Float API uses 'modified', not 'updated_at'
      created_by: z.number().nullable().optional(),
      modified_by: z.number().nullable().optional(),
      active: z.number().nullable().optional(), // 0 = archived, 1 = active
      priority: z.number().nullable().optional(), // Priority level (1-5)
      completed: z.number().nullable().optional(), // 0 = not completed, 1 = completed
      completed_date: z.string().nullable().optional(),
      notes: z.string().nullable().optional(),
      color: z.string().nullable().optional(),
      reminder_date: z.string().nullable().optional(),
      reminder_sent: z.number().nullable().optional(), // 0 = not sent, 1 = sent
    });
Behavior2/5

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

No annotations provided, and the description does not disclose behavioral aspects such as read-only nature, pagination defaults, or side effects. It only states 'list' which implies reading, but lacks detail on data freshness, ordering, or limitations.

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?

A single, clear sentence that is front-loaded with the verb and resource. No superfluous words, achieving maximum conciseness for the purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (13 parameters, no output schema, no annotations), the description is too sparse. It lacks details on pagination behavior, default results, ordering, or return format, which are important for an agent to use the tool effectively.

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?

The schema provides full descriptions for all 13 parameters (100% coverage), so the description's mention of 'filtering by project, phase, status, or date range' adds only a high-level summary without new meaning. Baseline 3 is appropriate.

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 tool lists milestones with optional filters by project, phase, status, or date range. This distinguishes it from sibling tools like 'get-milestone' (single item) or 'get-project-milestones' (pre-filtered by project).

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. With many sibling list tools (e.g., list-phases, list-project-tasks), the description does not provide criteria for selecting this over others, nor does it mention when not to use it.

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/asachs01/float-mcp'

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